A Troubleshooting the Installation Process

This appendix provides troubleshooting information for installing Oracle Clusterware and Oracle Real Application Clusters (Oracle RAC). The topic in this appendix is:

Troubleshooting the Oracle Clusterware and Oracle RAC Installation

See Also:
Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide for additional information about Oracle Clusterware and Oracle RAC configuration and deployment.

Troubleshooting the Oracle Clusterware and Oracle RAC Installation

This section contains these topics:

General Installation Issues
Oracle Clusterware Install Actions Log Errors and Causes
Real Application Clusters Installation Error Messages
Performing Cluster Diagnostics During Real Application Clusters Installations

General Installation Issues

The following is a list of examples of types of errors that can occur during installation:

Nodes unavailable for selection from the OUI Node Selection screen: Cause: Oracle Clusterware is either not installed, or the Oracle Clusterware services are not up and running.; Action: Install Oracle Clusterware, or review the status of your Oracle Clusterware. Consider restarting the nodes, as doing so may resolve the problem.

Node nodename is unreachable

Cause: Unavailable IP host

Action: Attempt the following:

Run the command ipconfig /all. Compare the output of this command with the contents of the C:\WINNT\system32\drivers\etc\hosts file to ensure that the node IP is listed.
Run the command nslookup to see if the host is reachable.

Time stamp is in the future

Cause: One or more nodes has a different clock time than the local node. If this is the case, then you may see output similar to the following:

time stamp 2005-04-04 14:49:49 is 106 s in the future

Action: Ensure that all member nodes of the cluster have the same clock time.

Administrative user unable to log in to SQL*Plus using the SYSDBA role: Cause: When you install Oracle Database on Microsoft Windows, Oracle Universal Installer creates a Windows local group called ORA_DBA, and then adds your Windows username to it. Members of ORA_DBA automatically receive the SYSDBA privilege. However, for cluster installations, Oracle Universal Installer does not add the user to ORA_DBA if they have performed the installation remotely. As a result, this user cannot log in to SQL*Plus using the SYSDBA role; Action: Manually add remote users to ORA_DBA.

Oracle Clusterware Install Actions Log Errors and Causes

The following is a list of potential errors in the installActions.log:

PRIF-10: failed to initialize the cluster registry

Configuration assistant "Oracle Private Interconnect Configuration Assistant" failed
Step 4: Starting up CRS stack on all nodes

node1 service OracleCSService in improper STOPPED state, err(997)

node2 service OracleCSService in improper STOPPED state, err(997)
Step 4: Starting up CRS stack on all nodes

node1 service OracleCSService in improper STOPPED state, err(0)

node2 service OracleCSService in improper STOPPED state, err(997)
Step 4: Starting up CRS stack on all nodes

oracletest1 failed to startup service OracleEVMService, err(1053)
Step 1: checking status of CRS cluster

Step 2: configuring OCR repository

ignoring upgrade failure of ocr(-1073740972)

failed to configure Oracle Cluster Registry with CLSCFG, ret -1073740972

after installing the patch 3555863 the configuration fails with the same

problem

Each of these error messages can be caused by one of the following issues:

The OCFS format is not recognized on one or more of the remote cluster nodes

If you are using OCFS for your OCR and Voting disk partitions, then:

Leave the OUI window in place.
Restart the second node, and any additional nodes.
Retry the assistants

Timing issue with start of the OracleCSService:

If you think the cause may be a timing issue, then:

Leave the OUI window in place.
Start the OracleCSService manually on all nodes. You may also need to start the OracleObjectService manually.
Retry the assistants

You are on a Windows 2003 system, and Automount of new drives is not enabled:

If this is true, then:

For Oracle RAC on Windows 2003, you must issue the following commands on all nodes:

diskpart
automount enable

If you are already failing at the configuration assistants and this has not yet been run on all nodes in the cluster, you will need to clean up your CRS install, issue this command on all nodes, reboot all nodes, and start the CRS install again.

You have entered a period in one of the node names during CRS install

Periods (".") are not permitted in node names. Instead, use an underscore character ("_") or a hyphen. ("-").

To resolve a failed installation, remove traces of the Oracle installation, and reinstall with a permitted node name.

Node1 failed to startup service OracleEVMService, err(1053)

The installation requires dll: MSVCP60.DLL. Copying MSVCP60.DLL to c:\winnt\system32 should allow EVM to start.

Ignoring upgrade failure of ocr(-1073740972)

This error indicates that the user that is performing installation does not have Administrator privileges.

Real Application Clusters Installation Error Messages

Real Application Clusters Management Tools Error Messages are in Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide.

Performing Cluster Diagnostics During Real Application Clusters Installations

If Oracle Universal Installer (OUI) does not display the Node Selection page, then perform clusterware diagnostics by running the olsnodes -v command from the binary directory in your Oracle Clusterware home, CRS_home\BIN, 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.