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

OCR Dump (ocrdump) Utility
The primary function of this utility is to dump the contents of the OCR into an ASCII readable format file. The output file
is created in the directory where the utility is executed. If no file name is specified, the dump is created in OCRDUMPFILE
within the same directory. The utility also generates a log file in the directory from which the ocrdump was executed.

[root@ssky3l12p2 ~]# /u01/app/12.1.0/grid/bin/ocrdump [<filename>]

In addition, partial dump outputs can be generated by specifying - keyname <keyword> with the ocrdump
command. For example, to generate a dump of all SYSTEM -level definitions, the following syntax should be followed:

[root@ssky3l12p2 ~]# /u01/app/12.1.0/grid/bin/ocrdump -keyname SYSTEM OCRsystemDUMP

Workshop
There could be several reasons why the Oracle-related resources managed by the clusterware do not start on reboot.
As a normal practice, one should check the clusterware-related log files. Figure 16-3 illustrates the list of log files
generated by the various daemon processes running at the clusterware level. Most logs have a retention policy of
capping at 50MB per file and keeping 10 logs per log type. For example, the list of logs created for CSSD are listed below.

acfs

ohasd
crsd
cssd

orarootagent_root
oragent_oracle
oracssdmonitor_root GRID HOME

evmd
agent
gpnpd
gnsd

oracssdagent_root

diag

orarootagent_root
oragent_oracle

<nodename>
e.g.. ssky1l1p1

client
gipcd
diskmon

log

scriptagent_oracle

srvm

crs

admin
ctssd

mdnsd
racg

racgmain
racgevtf
racgeut

cvu

crflogd
crfmond

alert<nodename>.log

Figure 16-3. Clusterware-related log directories