This appendix provides troubleshooting information for Oracle Real Application Clusters (Oracle RAC).
See Also:The Oracle Database 11g release 1 (11.1) Oracle Real Application Clusters documentation set included with the installation media in the Documentation directory:
Oracle Real Application Clusters Administration and Deployment Guide
This section contains these topics:
The following is a list of examples of types of errors that can occur during installation. It contains the following issues:
/etc/oratabpointing to a non-existent Oracle home. The OUI error file should show the following error: "
java.io.IOException: /home/oracle/OraHome//bin/kfod: not found"
/etc/oratabpointing to a non-existing Oracle home.
$ xhost somehost.example.com
Then, enter the following commands, where
workstation_name is the host name or IP address of your workstation.
Bourne, Bash, or Korn shell:
$ DISPLAY=workstation_name:0.0 $ export DISPLAY
To determine if X Window applications display correctly on the local system, enter the following command:
The X clock should appear on your monitor.If the X clock appears, then close the X clock and start Oracle Universal Installer again.
Run the command
ifconfig -a. Compare the output of this command with the contents of the
/etc/hosts file to ensure that the node IP is listed.
Run the command
nslookup to see if the host is reachable.
oracle user, attempt to connect to the node with
rsh. If you are prompted for a password, then user equivalence is not set up properly. Contact your system administrator, or consult Oracle Clusterware Installation Guide for your platform to complete SSH configuration.
rootupgrade.sh. To confirm, look for the error "utopen:12:Not enough space in the backing store" in the log file
/var/opt/oracle/srvConfig.loc, and copy the contents of this raw device to the new device using the command
http://www.unixodbc.org, and restart the installation. This is a requirement for Oracle RAC databases, documented in system requirements in the Oracle Clusterware installation guide for your platform.
time stamp 2005-04-04 14:49:49 is 106 s in the future
nscdhas not been activated.
/sbin/service nscd start
Note that the user performing the Oracle RAC installation must have membership both in the oinstall group and the OSDBA group (typically
dba). If this is not the case, then the installation will fail
If Oracle Universal Installer (OUI) does not display the Node Selection page, then perform clusterware diagnostics by running the
-v command from the binary directory in your Oracle Clusterware home
(CRS_home) and analyzing its output. Refer to your clusterware documentation if the detailed output indicates that your clusterware is not running.
In addition, use the following command syntax to check the integrity of the Cluster Manager:
cluvfy comp clumgr -n node_list -verbose
In the preceding syntax example, the variable
node_list is the list of nodes in your cluster, separated by commas.
During an installation, Oracle Universal Installer records all of the actions that it performs in a log file. If you encounter problems during the installation, then review the log file for information about possible causes of the problem.
To view the log file, follow these steps:
If necessary, enter the following command to determine the location of the oraInventory directory:
$ cat /opt/oracle/oraInst.loc
Enter the following command to determine the name of the log file:
$ ls -ltr
This command lists the files in the order of creation, with the most recent file shown last. Installer log files have names similar to the following, where
date_time indicates the date and time that the installation started:
To view the most recent entries in the log file, where information about a problem is most likely to appear, enter a command similar to the following:
$ tail -50 installActions2007-07-20_09-53-22AM.log | more
This command displays the last 50 lines in the log file, and enables you to page through them.
If the error displayed by Oracle Universal Installer or listed in the log file indicates a relinking problem, then refer to the following file for more information:
To troubleshoot an installation error that occurs when a configuration assistant is running:
Review the installation log files listed in the section""Reviewing the Log of an Installation Session".
Review the specific configuration assistant log file located in the
$ORACLE_HOME/cfgtoollogs directory. Try to fix the issue that caused the error.
If you see the "Fatal Error. Reinstall" message, then look for the cause of the problem by reviewing the log files. Refer to the section "Fatal Errors" for further instructions.
This section contains the following topics:
Oracle configuration assistant failures are noted at the bottom of the installation screen. The configuration assistant interface displays additional information, if available. The configuration assistant execution status is stored in the following file:
More details on errors related to the configuration assistant can be found under the following directory:
The completion status codes are listed in the following table:
Status Result Code Configuration assistant succeeded 0 Configuration assistant failed 1 Configuration assistant cancelled -1
If you receive a fatal error while a configuration assistant is running, you must complete the following tasks:
Deinstall Oracle software.
Correct the cause of the fatal error.
Reinstall the Oracle software.