While I installing Windows Failover Cluster system, I get an error like “Cluster Disk 1 does not support persistent reservations.”. If you are attempting to set up a Cluster in a Single Host, and the shared disk (or disks) for the cluster is RDM (Raw Device Mapping, or Raw Disk Mapping), in Physical Compatibility Mode. If this is the case, you can either change the disks to Virtual Compatibility mode, or if you wish to use Physical Compatibility Mode, the cluster nodes must be on different hosts. My case was that.
Other Cause For This Error
If the storage array is not configured correctly to support SCSI-3 compliant commands.
A third-party plug-in is interfering with the SCSI reservation process (such as the PowerPath/VE PSA).
If virtual machines are running under the MSCS configuration on two separate ESX/ESXi hosts, and the .vmdk files are on a VMFS datastore which is configured as physical bus sharing mode.
I upgraded MsSQL database version from MsSQL Server 2008 Express Edition to MsSQL Server 2008 Enterprise Edition. After upgrade operation, Agent XPs was disabled and MsSQL Server Agent servis could not start. I reconfigured Agent XPs configuration. The problem resolved.
Management Studio Object Explorer does not display the contents of the SQL Server Agent node unless these extended stored procedures are enabled regardless of the SQL Server Agent service state.
Agent XPs Possible Values
0, indicating that SQL Server Agent extended stored procedures are not available (the default). 1, indicating that SQL Server Agent extended stored procedures are available.
Show Current Value
EXEC SP_CONFIGURE ‘Agent XPs’
Reconfigure Agent XPs
EXEC SP_CONFIGURE ‘show advanced options’, 1;
SP_CONFIGURE ‘Agent XPs’, 1;
After these parameter change operations you can restart agent service or sql server service to show Agent XPs enabled.
Use lightweight jobs when you have many short-duration jobs that run frequently. Under certain circumstances, using lightweight jobs can deliver a small performance gain.
Lightweight jobs have the following characteristics:
Unlike regular jobs, they are not schema objects.
They have a significant improvement in create and drop time over regular jobs because they do not have the overhead of creating a schema object.
They have lower average session creation time than regular jobs.
They have a small footprint on disk for job metadata and runtime data.
You designate a lightweight job by setting the job_style job attribute to LIGHTWEIGHT. The other job style is REGULAR, which is the default.
Like programs and schedules, regular jobs are schema objects. In releases before Oracle Database 11g Release 1, regular jobs were the only job style supported by the Scheduler.
A regular job offers the maximum flexibility but does entail some overhead when it is created or dropped. The user has fine-grained control of the privileges on the job, and the job can have as its action a program or a stored procedure owned by another user.
I got an error like CRS-0184 on Oracle 11g RAC system, because of interconnect network is down. After network was up, CRS Daemon did not start. You can take these errors like CRS-0184, CRS-2674, CRS-4534, CRS-4530.. I resolved that problem with below operations.
That scenario is required that we need to fetch data from the customer’s existing third party application. For example the customer is having some websites where the enquiries are being stored. Or The company employees who are on tour log their requests for leave in the portal. In such case we may have to provide an interface between their existing application to the upcoming SAP system. It is possible that the system is using a different database altogather. So in that situation how a connectivity is established between the SAP database and External Application database.
You can create connection to external database with below processes.
1 – Connection check from SAP to External Database
You have to access external database from SAP network. You can check firewall, telnet configuration.