Owner's Manual

58 Deployment Guide
CRS CRS gives up
prematurely when
trying to start.
Due to Oracle bug
4698419. See the
Oracle Metalink
website at
metalink.oracle.com.
Apply patch 4698419 available on the Oracle Metalink
website at metalink.oracle.com.
CRS The Oracle
Clusterware
installation
procedure fails.
EMC PowerPath
device names are not
uniform across the
nodes.
Before you install Oracle Clusterware, restart PowerPath
and ensure that the PowerPath device names are
uniform across the nodes.
CRS CRS fails to start
when you reboot
the nodes, or type
/etc/ini.d/ini
t.crs start.
The Cluster Ready
Services CSS
daemon cannot write
to the quorum disk.
• Attempt to start the service again by rebooting the
node or typing
root.sh from
/crs/oracle/product/10.2.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.
CRS When you run
root.sh, CRS fails
to start.
Check and make sure
you have public and
private node names
defined and that 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/10.2.0/crs/ after correcting the
networking issues.
CRS When you run
root.sh, CRS fails
to start.
The 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/10.2.0/crs/.
Table 1-9. Troubleshooting (continued)
Category Problem / Symptom Cause Recommended Corrective Action