Enabling Oracle Cluster Synchronization Service daemon to start automatically

For Oracle 11g R2 or 12c, perform the following procedure on each node of the cluster.

The Oracle ASM instance resource faults if the required Oracle Cluster Synchronization Services process (occsd.bin) is not active. To prevent the resource from faulting, modify the AUTO_START attribute of the CSSD resource (ora.cssd). This configuration change enables the Oracle High Availability Services daemon (ohasd) to start the ocssd.bin process as soon as the ohasd daemon starts on each node in the cluster.

Thus, when the ocssd.bin process starts, it automatically starts up for the ASM instance. However, this could cause concurrency violation issues if the ASMInst resource is configured as a part of failover service group in the following scenario. Suppose a node goes down or reboots for some reason, all the resources on this node comes online on the second node. After the reboot, the ohasd process automatically starts the ocssd.bin process, which automatically starts the ASM instance on node1 which leads to concurrency violation. To resolve this issue, recommends you to disable automatic startup of asm by running the following command:

# $GRID_HOME/bin/crsctl modify resource ora.asm -attr AUTO_START=never

Note:

You must run the command to disable automatic startup of asm on all nodes in the VCS cluster that have Oracle Grid Infrastructure installed.

To enable Oracle Cluster Synchronization Service daemon to start automatically