Owner's Manual

Troubleshooting 17
When you run root.sh, CRS fails to start.
NOTE: Ensure that you have all the public and private node names defined and you
can ping the node names.
Attempt to start the service again by rebooting the node or by running
root.sh from /crs/oracle/product/11.1.0/crs/ after correcting the
networking issues.
The following are the list of issues that can result in CRS failure:
• OCR file and Voting disk are inaccessible.
Correct the I/O problem and attempt to start the service again by
rebooting the node or by running
root.sh from
/crs/oracle/product/11.1.0/crs/.
• OCR file and Voting disk have not been cleared and contain
old information.
Clear the OCR and Voting disks to erase the old information.
You can do this on RHEL4 by entering the following lines:
dd if=/dev/zero of=/dev/raw/ocr.dbf
dd if=/dev/zero of=/dev/raw/votingdisk
Attempt to start the service again by rebooting the node or by running
root.sh from /crs/oracle/product/11.1.0/crs/.
• The Oracle User does not have permissions on /var/tmp
(specifically
/var/tmp/.oracle ).
a Make User Oracle the owner of /var/tmp/.oracle by entering the
following command:
chown oracle.oinstall /var/tmp/.oracle
b Attempt to start the service again by rebooting the node or by running
root.sh from: /crs/oracle/product/11.1.0/crs/.