Owner's Manual

Deployment Guide 59
CRS When you run
root.sh following
reinstallation, CRS
fails to start.
The OCR file and
Voting disk have not
been cleared and
contain old
information.
1 Clear the OCR and Voting disks by typing the
following lines:
dd if=/dev/zero of=/dev/raw/ocr.dbf
dd if=/dev/zero of=
/dev/raw/votingdisk
2 Attempt to start the service again by rebooting the
node or by running
root.sh from
/crs/oracle/product/10.2.0/crs/
CRS When you run
root.sh, CRS fails
to start.
The user oracle does
not have permissions
on /var/tmp
(specifically
/var/tmp/.oracle).
1 Make user oracle the owner of /var/tmp/.oracle by
typing
chown oracle.oinstall
/var/tmp/.oracle
2 Attempt to start the service again by rebooting the
node or by running
root.sh from:
/crs/oracle/product/10.2.0/crs/
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
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
Table 1-9. Troubleshooting (continued)
Category Problem / Symptom Cause Recommended Corrective Action