Skip Headers
Oracle® Real Application Clusters Installation Guide
11g Release 1 (11.1) for Microsoft Windows

B28251-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

A Troubleshooting the Installation Process

This appendix provides troubleshooting information for installing Oracle Real Application Clusters (Oracle RAC). The topics in this appendix are:

A.1 Troubleshooting Oracle RAC Installations

This section contains these topics:

A.1.1 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:
  1. 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.

  2. 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 the name of the user performing the software installation to this group. Members of the ORA_DBA group automatically receive the SYSDBA privilege. Oracle Universal Installer does not add the software owner user to ORA_DBA on other nodes under the following circumstances:
  • The installation user performed the installation remotely

  • The user performing the installation is a local user and not a Windows domain user

As a result, this user cannot log in to SQL*Plus using the SYSDBA role.

Action: Manually add remote users to ORA_DBA on the other nodes in the cluster.

A.1.2 Oracle Real Application Clusters Installation Error Messages

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

A.1.3 Performing Cluster Diagnostics During Oracle 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.

A.2 Verifying Requirements

Before you try any of the troubleshooting steps in this appendix, do the following:

A.3 Encountering Installation Errors

If you encounter an error during installation:

A.4 Reviewing the Log of an Installation Session

During an installation, Oracle Universal Installer records all the actions that it performs in a log file. If you encounter problems during the installation, review the log file for information about possible causes of the problem. By default, the log files are located in the following directory:

SYSTEM_DRIVE:\> Program Files\Oracle\Inventory\logs

Log filenames from interactive installations take the form:

installActionsdate_time.log

For example, if an interactive installation occurred at 9:00:56 a.m. on October 14, 2005, the log file would be named:

installActions2006-10-14_09-00-56AM.log

Note:

Do not delete or manually alter the Inventory directory or its contents. Doing so can prevent Oracle Universal Installer from locating products that you install on your system.

A.5 Silent or Noninteractive Installation Response File Error Handling

To determine whether a silent or noninteractive installation succeeds or fails, check the silentInstallActionsdate_time.log file, located in DRIVE_LETTER:\Program Files\Oracle\Inventory\logs.

If necessary, see the previous section for information about determining the location of the Inventory directory.

A silent or noninteractive installation fails if:

Oracle Universal Installer or a configuration assistant validates the response file at runtime. If the validation fails, the silent or noninteractive installation or configuration process ends. Oracle Universal Installer treats values for parameters that are of the wrong context, format, or type as if no value was specified in the file.

See Also:

"Reviewing the Log of an Installation Session" for information about interactive installation log files

A.6 Troubleshooting Oracle Configuration Manager

This section lists some of the errors that may occur while using Oracle Configuration Manager and provides tips to troubleshoot these errors.

A.7 Troubleshooting Configuration Assistants

To troubleshoot an installation error that occurs when a configuration assistant is running:

A.7.1 Configuration Assistant Failures

Oracle configuration assistant failures are noted at the bottom of the installation window. The configuration assistant interface displays additional information, if available. The configuration assistant execution status is stored in the installActionsdate_time.log file.

The execution status codes are listed in the following table:

Status Result Code
Configuration assistant succeeded 0
Configuration assistant failed 1
Configuration assistant canceled -1

A.7.2 Fatal Errors

If you receive a fatal error while a configuration assistant is running:

  1. Remove the failed installation as described in the "Cleaning Up After a Failed Installation" section.

  2. Correct the cause of the fatal error.

  3. Reinstall the Oracle software.

A.8 Cleaning Up After a Failed Installation

If an installation fails, then you must remove files that Oracle Universal Installer created during the attempted installation and remove the Oracle home directory. Follow the instructions in Chapter 7, "Removing Oracle Database Software" to run Oracle Universal Installer to deinstall Oracle Clusterware, manually remove the Oracle directory, and remove Oracle from the Registry Editor keys. Afterward, reinstall the software.

A.9 Online Help Not Working

If users are accessing Oracle Application Express through a Virtual Host, online Help will not work. Consider the following example:

In this example, Oracle Application Express online Help will not work if the users cannot access internal.server.com. To resolve this issue, add the following lines to the Oracle Application Express Database Access Descriptor (DAD) to override the CGI environment variables SERVER_NAME and SERVER_PORT:

PlsqlCGIEnvironmentList SERVER_NAME=external.server.com
PlsqlCGIEnvironmentList SERVER_PORT=80

See Also:

Oracle HTTP Server mod_plsql User's Guide for information on overriding the CGI environment variables