Skip Headers
Oracle® Database Client Installation Guide
11g Release 2 (11.2) for Microsoft Windows

E47959-02
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

D Troubleshooting the Oracle Database Client Installation

This appendix contains the following information about troubleshooting:

D.1 Verifying Requirements

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

D.2 What to Do if an Installation Error Occurs?

If you encounter an error during installation:

D.3 Reviewing the Log of an Installation Session

When you run Oracle Universal Installer on a computer with no Oracle software installed, it creates a directory called:

DRIVE_LETTER:\Program Files\Oracle\Inventory\logs

During this first installation and all subsequent installations, Oracle Universal Installer saves all of the actions that it performs in a log file in this directory. If you encounter problems during the installation, review the log file for information about possible causes of the problem.

Log filenames for 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 February 14, 2005, the log file would be named:

installActions2005-02-14_09-00-56-am.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.

D.4 Silent-Mode Response File Error Handling

To determine whether a silent or response file mode installation succeeds or fails, check the silentInstallActionsdate_time.log file, located in the DRIVE_LETTER:\Program Files\Oracle\Inventory\logs 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 installation or configuration process ends.

See Also:

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

D.5 Troubleshooting Configuration Assistants

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

  • Review the installation log files listed in Section D.3, "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, look for the cause of the problem by reviewing the log files. Refer to "Irrecoverable Errors" for further instructions.

D.5.1 Configuration Assistant Failure

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

D.5.2 Irrecoverable Errors

If you receive an irrecoverable error while a configuration assistant is running:

  1. Remove the failed installation as described in Section D.7, "Cleaning Up After a Failed Installation."

  2. Correct the cause of the irreoverable error.

  3. Reinstall the Oracle software.

D.6 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 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.

D.7 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 Chapter 5, "Removing Oracle Database Client Software" to run the Deinstallation tool.