Owner's Manual

16 Troubleshooting
$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
Check /
var/log/messages for any error messages regarding CRS init scripts.
Capture all log files for support diagnosis.
Node continuously reboots
Node reboots continuously when the node does not have access to the
quorum disk on shared storage.
Perform the following steps:
a Start Linux in single-user mode and enter the following command:
/etc/init.d/init.crs disable
b Verify that the quorum disk is available and the private interconnect
is alive.
c Reboot and type: /etc/init.d/init.crs enable
If the private interconnect is down:
a Start Linux in single-user mode.
b Enter the following command:
/etc/init.d/init.crs disable
c Verify that the node can ping over the private interconnect to the
remaining nodes in the cluster.
d Enter the following command:
/etc/init.d/init.crs enable
Reboot the system. 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