12 Troubleshooting
CRS fails to start when you reboot the nodes, or after entering
/etc/init.d/init.crs start
CRS fails to start when the Cluster Ready Services CSS daemon is unable to
write to the quorum disk.
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 logged in as
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), then
verify the following:
•The
/etc/hosts
file on each node contains the correct IP addresses for all
node hostnames, including the virtual IP addresses.
• You can ping the public and private hostnames.
• The Oracle Cluster Registry (OCR) file and Voting disk is writable.
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 is 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.
To Next Page
Loading...
