F Troubleshooting the Oracle Database Installation

F.1 Verifying Requirements

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

• Check Chapter 2, "Oracle Database Preinstallation Requirements" to ensure that the system meets the requirements and that you have completed all of the preinstallation tasks.

• Read the release notes for the product on your platform before installing it. The release notes are available on the Oracle Database installation media. You can find the latest version of the release notes on the Oracle Technology Network Web site:

  http://www.oracle.com/technetwork/index.html
  

F.2 Encountering Installation Errors

If you encounter an error during installation:

• Do not exit Oracle Universal Installer.

• If you clicked Next after you entered incorrect information about one of the installation windows, click Back to return to the window and correct the information.

• If you encounter an error while Oracle Universal Installer is copying or linking files, see "Reviewing the Log of an Installation Session" for interactive installations or "Silent Mode Response File Error Handling" for more information.

• If you encounter an error while a configuration assistant is running, see the "Troubleshooting Configuration Assistants" section.

• If you cannot resolve the problem, remove the failed installation by following the steps listed in the "Cleaning Up After a Failed Installation" section.

F.3 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
oraInstalldate_time.err
oraInstalldate_time.out

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

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

F.4 Silent Mode Response File Error Handling

To determine whether a silent-mode 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 installation fails if:

• You do not specify a response file.

• You specify an incorrect or incomplete response file.

• Oracle Universal Installer encounters an error, such as insufficient disk space.

Oracle Universal Installer or a configuration assistant validates the response file at run time. If the validation fails, the silent-mode installation or configuration process ends.

F.5 Troubleshooting Host Name Changes and CSS

If you change the host name for Oracle Automatic Storage Management, then the Oracle CSS service does not start. To solve this issue, perform the following steps:

1. Log in as a user with Administrator privileges.

2. Run roothas.pl to deconfigure CSS.

   C:\> cd \app\oracle\product\11.2.0\grid\crs\install
   perl roothas.pl -deconfig -force
   

   This removes any configuration related files on the system that referenced the old host name.

3. Run gridconfig.bat script to reconfigure CSS using the new host name:

   C:\> cd \app\oracle\product\11.2.0\grid\crs\config
   gridconfig.bat
   

4. Go to the grid home's bin directory. Use the srvctl add database command with the -c SINGLE flag to add the database in an Oracle Restart configuration. Also use the srvctl add command to add the listener, the Oracle ASM instance, all Oracle ASM disk groups, and any database services to the Oracle Restart configuration.

   See Also:

   "srvctl add" in Oracle Database Administrator's Guide

F.6 Troubleshooting Configuration Assistants

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

• Review the installation log files listed in the "Reviewing the Log of an Installation Session" section.

• Review the specific configuration assistant log file located in the ORACLE_BASE\cfgtoollogs directory. Try to fix the issue that caused the error.

  Note:

  Ensure that there is no space in the path.

• If you see the "Fatal Error. Reinstall message", look for the cause of the problem by reviewing the log files. See "Irrecoverable Errors" for more information.

F.7 Troubleshooting Inventory Issues

If you face any of the following situations for Oracle home, then run the opatch lsinventory -detail command to list the contents of the inventory and see section "Recovering from inventory corruption" in the Oracle Universal Installer and OPatch User's Guide for Windows and UNIX for information about fixing the issue.

• Oracle home is cloned without completing the inventory steps.

• There is bad inventory.

• Inventory is not available but it is created when the Oracle Enterprise Manager Agent is installed in a separate Oracle home.

F.8 Troubleshooting Screen Display Issues

If you connect to Oracle database with the screen resolution 640 X 480 or 800 X 600, then the Next button in the GUI is not visible as it hides behind the Taskbar. In order to counter this problem, do one of the following:

• Hide the Taskbar.

• Move the Oracle Universal Installer screen up.

• Set the screen resolution to 1024 X 768 or higher.

F.9 Cleaning Up After a Failed Installation

If an installation fails, you must remove files that Oracle Universal Installer created during the attempted installation and remove the Oracle home directory.

Follow the instructions in "Removing Oracle Database Software" to run the Deinstallation tool.