A Troubleshooting Oracle Real Application Clusters Installations

A.1 Troubleshooting Oracle RAC Installation Errors

The following information explains how to proceed if you encounter an error during installation of Oracle RAC.

%SYSTEMDRIVE%\Program Files\Oracle\Inventory\logs

installActionsdate_time.log

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

A.2 Resolving Oracle RAC Installations Errors

This section contains the following topics:

• General Installation Issues

• Performing Cluster Diagnostics During Oracle RAC Installations

• Reviewing the Log of an Installation Session

cluvfy comp clumgr -n node_list -verbose

A.3 Troubleshooting Configuration Assistant Errors

To troubleshoot an installation error that occurs when a configuration assistant is running, do the following:

• Review the installation log files listed in the section Section A.3.1, "Reviewing Configuration Assistant Errors.".

• Review the specific configuration assistant log file located in the Oracle base directory, in the path %ORACLE_BASE%\cfgtoollogs. 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. See the section Section A.3.3, "Resolving Irrecoverable Errors Reported by Configuration Assistants" for further instructions.

C:\Program Files\Oracle\Inventory\logs\installActionsdate_time.log

ORACLE_BASE\cfgtoollogs

A.4 Troubleshooting Silent or Noninteractive Installations

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, as described in Section A.2.3, "Reviewing the Log of an Installation Session."

A silent or noninteractive installation fails if:

• You do not specify a response file.

• You specify an incorrect or incomplete response file.

  For example, a common problem is that while all the product-specific data is correct, the staging area location may be incorrect. If this is the case, then check the FROM_LOCATION variable and ensure that it points to the products.xml file in the installation media. In the installation media, this products.xml is in database\stage.

• OUI encounters an error, such as insufficient disk space.

OUI or a configuration assistant validates the response file at run time. If the validation fails, then the silent or noninteractive installation or configuration process ends. OUI treats values for parameters that are of the wrong context, format, or type as if no value had been specified in the file.

A.5 About Using CVU Cluster Healthchecks After Installation

Starting with Oracle Grid Infrastructure 11g release 2 (11.2.0.3) and later, you can use the CVU healthcheck command option to check your Oracle Clusterware and Oracle Database installations for their compliance with mandatory requirements and best practices guidelines, and to ensure that they are functioning properly.

Use the following syntax to run the healthcheck command option:

cluvfy comp healthcheck [-collect {cluster|database}] [-db db_unique_name] [-bestpractice|-mandatory] [-deviations] [-html] [-save [-savedir directory_path]

For example:

$ cd /home/grid/cvu_home/bin
$ ./cluvfy comp healthcheck -collect cluster -bestpractice -deviations -html

The options are:

• -collect [cluster|database]

  Use this flag to specify that you want to perform checks for Oracle Clusterware (cluster) or Oracle Database (database). If you do not use the collect flag with the healthcheck option, then cluvfy comp healthcheck performs checks for both Oracle Clusterware and Oracle Database.

• -db db_unique_name

  Use this flag to specify checks on the database unique name that you enter after the db flag.

  CVU uses JDBC to connect to the database as the user cvusys to verify various database parameters. For this reason, if you want checks to be performed for the database you specify with the -db flag, then you must first create the cvusys user on that database, and grant that user the CVU-specific role, CVUSAPP. You must also grant members of the CVUSAPP role SELECT permissions on system tables.The SQL script cvusys.sql is included in the CVU_home/cv/admin directory to facilitate the creation of this user. Use this SQL script to create the cvusys user on all the databases that you want to verify using CVU.

  If you use the db flag but do not provide a database unique name, then CVU discovers all the Oracle Databases on the cluster. If you want to perform best practices checks on these databases, then you must create the cvusys user on each database, and grant that user the CVUSAPP role with the SELECT privileges needed to perform the best practice checks.

• [-bestpractice | -mandatory] [-deviations]

  Use the bestpractice flag to specify best practice checks, and the mandatory flag to specify mandatory checks. Add the deviations flag to specify that you want to see only the deviations from either the best practice recommendations or the mandatory requirements. You can specify either the -bestpractice or -mandatory flag, but not both flags. If you specify neither -bestpractice or -mandatory, then both best practices and mandatory requirements are displayed.

• -html

  Use the html flag to generate a detailed report in HTML format.

  If you specify the html flag, and a browser CVU recognizes is available on the system, then the browser is started and the report is displayed on the browser when the checks are complete.

  If you do not specify the html flag, then the detailed report is generated in a text file.

• -save [-savedir dir_path]

  Use the save or -save -savedir flags to save validation reports (cvuchecdkreport_timestamp.txt and cvucheckreport_timestamp.htm), where timestamp is the time and date of the validation report.

  If you use the save flag by itself, then the reports are saved in the path CVU_home/cv/report, where CVU_home is the location of the CVU binaries.

  If you use the flags -save -savedir, and enter a path where you want the CVU reports saved, then the CVU reports are saved in the path you specify.

A.6 Cleaning Up After a Failed Installation

If an installation fails, then you must remove the Oracle home directory and remove all files that OUI created during the attempted installation. Perform the following steps to clean up the failed installation:

1. Follow the instructions in Chapter 8, "Removing Oracle Real Application Clusters Software" to run OUI to deinstall Oracle RAC.

2. Manually remove the directory that was used as the Oracle home directory during the installation.

3. Remove the following Windows Registry keys created by OUI during the previous installation attempt:

   HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Oracle11\Performance
    \KEY_ORACLE_HOME_NAME
   

After you have completed these steps, you can start the installation again.