Owner's Manual

6
• PROBLEM: CRS fails to start when you reboot the nodes, or after entering
/etc/ini.d/init.crs start .
–
CAUSE: The Cluster Ready Services CSS daemon cannot write to the
quorum disk.
–
RESOLUTION: Attempt to start the service again by rebooting the node
or typing
root.sh from /crs/oracle/product/11.1.0/crs/ .
Verify that each node has access to the quorum disk and the user
root can
write to the disk.
Check the last line in the file
$ORA_CRS_HOME/css/log/ocssd.log .
If you see
clssnmvWriteBlocks: Failed to flush writes
to (votingdisk)
, verify the following:
• The
/etc/hosts file on each node contains correct IP addresses for all
node hostnames, including the virtual IP addresses.
• You can ping the public and private hostnames.
• The quorum disk is writable.
•
PROBLEM: When you run root.sh , CRS fails to start.
–
CAUSE: Check and make sure you have public and private node names
defined and that you can ping the node names.
–
RESOLUTION: 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.
•
PROBLEM: When you run root.sh , CRS fails to start.
–
CAUSE: The OCR file and Voting disk are inaccessible.
–
RESOLUTION: 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/ .