Owner's Manual

Deployment Guide 49
CRS When you run
root.sh, CRS fails
to start.
The oracle user does not
have permissions on
/var/tmp (specifically
/var/tmp/.oracle).
1 Make oracle user 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:
/opt/oracle/product/10.1.0/crs_1/
CRS When you run
root.sh, CRS fails
to start.
Other CRS troubleshooting
steps have been 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: /opt/oracle/product/10.1.0/crs_1/
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 Type:
/etc/inet.d/init.crs disable
3 Verify that the quorum disk is available for read
and write. If it is not available, check hardware
connections and ensure that OCFS volumes are
mounted.
4 Reboot and type /etc/inet.d/init.crs
enable
Oracle
Installation
The root.sh script
fails.
The environment variable
LD_ASSUME_KERNEL
is missing.
1 Open a terminal window.
2 As root , type: LD_ASSUME_KERNEL-2.4.19
3 In the same terminal window as root ,
run
root.sh .
Table 1-8. Troubleshooting (continued)
Category Problem / Symptom Cause Recommended Corrective Action