Owner's Manual

54 Deployment Guide
CRS When you run
root.sh, CRS fails to
start.
Other CRS
troubleshooting steps
are attempted
without success.
1 Enable debugging by adding the following line to
root.sh :
set -x
2 Attempt to start the service again by running root.sh
from:
/crs/oracle/product/10.2.0/crs/
3 Check log files in the following directories to diagnose
the issue:
$ORA_CRS_HOME/crs/log
$ORA_CRS_HOME/crs/init
$ORA_CRS_HOME/css/log
$ORA_CRS_HOME/css/init
$ORA_CRS_HOME/evm/log
$ORA_CRS_HOME/evm/init
$ORA_CRS_HOME/srvm/log
4 Check /var/log/messages for any error messages
regarding CRS init scripts.
5 Capture all log files for support diagnosis.
CRS Node continually
reboots.
The node does not
have access to the
quorum disk on the
shared storage.
1 Start Linux in single user mode.
2 Ty p e :
/etc/inet.d/init.crs disable
3 Verify that the quorum disk is available and the private
interconnect is alive.
4 Reboot and type /etc/inet.d/init.crs
enable
CRS Node continually
reboots.
The private
interconnect is down.
1 Start Linux in single user mode.
2 Ty p e :
/etc/inet.d/init.crs disable
3 Verify that the node can ping over the private
interconnect to the remaining nodes in the cluster.
4 Ty p e :
/etc/inet.d/init.crs enable
5 Reboot your system.
6 In some cases, the network has a latency of up to
30 seconds before it can ping the remaining nodes in
the cluster after reboot. If this situation occurs, add
the following line to the beginning of your
/etc/inet.d/init.crs
file and reboot your system:
/bin/sleep 30
Table 1-9. Troubleshooting (continued)
Category Problem / Symptom Cause Recommended Corrective Action