Oracle Clusterware Diagnosis - Expert Oracle RAC Performance Diagnostics and Tuning - page 566

d. Oracle will update the ocr.loc file with the approprate information and make an entry

into the cluster alert log file on the node, as follows:

[root@ssky3l11p1 ~]# cat /etc/oracle/ocr.loc
#Device/file getting replaced by device +GRID_DATA2
ocrconfig_loc=+GRID_DATA
ocrmirrorconfig_loc=+GRID_DATA2
local_only=false

e. Verify the OCR file using the ocrcheck utility, as seen here:

[root@ssky3l11p1 ssky3l11p1]# /u01/app/12.1.0.1/grid/bin/ocrcheck
Status of Oracle Cluster Registry is as follows :
Version : 4
Total space (kbytes) : 409568
Used space (kbytes) : 1764
Available space (kbytes) : 407804
ID : 1514747975
Device/File Name : +GRID_DATA
Device/File integrity check succeeded
Device/File Name : +GRID_DATA2
Device/File integrity check succeeded

Device/File not configured

Device/File not configured

Device/File not configured

Cluster registry integrity check succeeded

Logical corruption check succeeded

Step 8
Now that both OCR files are fixed, restart the clusterware stack by using the /etc/init.d/init.ohasd start or the
$GRID_HOME/bin/crsctl start cluster commands. This will start the clusterware and the complete stack.

Step 9
If during the process the OHASD daemons were disabled to avoid a crash, they should now auto restart. One could
reset OHASD daemons to enable auto restart on reboot, as follows:

/etc/init.d/init.ohasd enable
/etc/init.d/init.ohasd start

Step 10
The ocr.loc file on the other nodes in the cluster will be automatically updated during subsequent restart of the
clusterware on the respective nodes.