ORA-29701 Unable To Connect To Cluster Synchronization Service

ORA-29701 Unable To Connect To Cluster Synchronization Service?

1. Check the ASM Instance:

ORA-29701 Unable To Connect To Cluster Synchronization Service? When you see the ORA-29701 error, it means that your cluster service is not starting. You can check this by running a command like $crsctlc check crs. If this command shows that CSS is not starting, you will need to restart it. To do this, you can follow these steps:

To start the cluster, you need to ensure that your CM is up and running. You can do this by running the following command:

This is often caused by a reboot of the node, especially when you restore or flashback a database. When you reboot the node, the CM is stopped and won’t start when it comes back online. Because of the TARGET=OFFLINE and AUTO_START=restore configuration. The same goes for the CSS.

To resolve this issue, you need to restart the CM and then retry the startup of the database. This will typically resolve the ORA-29701 error. If it doesn’t, you may need to contact Oracle support. If you do, make sure to provide the details of your problem and a case number if applicable.

2. Check the Grid Instance:

The Grid Instance is a set of data that can be accessed and updated via the Grid API. The Grid Instance contains all of the data that a Grid records. In the current group and in all previous groups. The Grid Instance is also used to synchronize changes to the database across all locations in the cluster. The Grid Instance provides high availability and scalability by ensuring that nodes in the cluster maintain the same state. It achieves this by using a consistent hash key to locate data on different. Servers and maintaining a single point of reference. This ensures that updates are not lost or accidentally repeated when a server fails.

The Domain Data Grid is designed to work out of the box in a wide variety of network topologies. Does not require additional configuration to operate. It is based on the principles of Oracle Coherence, which uses cluster consensus unambiguously. Determine ownership of information, and order operations that modify that information. And synchronize the results of those operations with other instances. This allows the Data Grid to deliver high availability and scalability without having to rely on any manual. Processes or external middleware.

You can use the cd command to navigate the resource tree and the help command to review manual pages for Data Grid CLI commands. You can also create aliases to define custom shortcuts for Data Grid commands.


3. Check the ASM Instance Instance:

The Oracle ASM instance must be running to synchronize time with the cluster. To check the status of the ASM instance, you can use the srvctl command. This command shows the status of the database and its disks. You can also see the current status of a specific disk by selecting it from the v$asm_disk_operation table.

The ASM_DISKGROUPS initialization parameter specifies a list of the names of the disk groups that an Oracle ASM instance mounts at startup. The default value for this parameter is a NULL string. This allows Oracle ASM to search a default path on your operating system for the disks that belong to any mounted disk group.

Each disk in a disk group has one or more mirrored copies of files in the same location on other disks in the disk group. This enables you to access a file in one location and then retrieve it from the other location. This is similar to operating system mirroring, but with one important difference: Oracle ASM mirrors at the file level while operating system mirroring mirrors at the disk level.

The Oracle ASM instance and the database instances must have read/write operating system permissions to the disks that comprise a disk group. These permissions are typically provided through shared Linux and UNIX group membership (OSASM group) or, on Windows systems, through the OS administrator role.

4. Check the ASM Instance Grid Instance:

When you use the Oracle installer to upgrade an existing Oracle Grid Infrastructure home to 11g release 2, it installs a new Oracle ASM instance in a separate Oracle Grid Infrastructure home. This type of upgrade is known as an out-of-place upgrade. To prevent issues when the Oracle ASM instance is upgraded to a different release, you must check whether or not the disk groups that are managed by the Oracle ASM instance are compatible with the Oracle ASM version that is being installed.

The ASM_DISKGROUPS parameter controls which disk groups are mounted automatically when the Oracle ASM instance starts up. This parameter is dynamic and Oracle ASM automatically adds the name of a disk group to this list if the disk group is successfully created or mounted. You must also manually remove the name of a disk group from this list if you no longer want the disk group to be mounted automatically at the Oracle ASM instance startup.

The ORACLEASM_DISK_SCANORDER and ORACLEASM_DISK_SCANEXCLUDE parameters determine which disks the Oracle ASM instance searches for and finds available storage on when performing a rebalance operation. If you are using Dell PowerPath, you must set these parameters to specify that the ORACLEASM_DISK_SCANORDER is set to emcpower:oracleasmlib:pwd and that the ORACLEASM_DISK_EXCLUDE is set to exclude disks. You must also set the ownership of the Oracle ASMLib devices to the same value as that used by the operating system on the operating node where the disks are stored.

Rasheed Alam

Add comment

Your Header Sidebar area is currently empty. Hurry up and add some widgets.