Skip Headers
Oracle® Database Client Installation Guide
10g Release 2 (10.2) for Microsoft Windows (64-Bit) on Intel Itanium

Part Number B14313-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
View PDF

C Troubleshooting the Oracle Database Client Installation

This appendix contains the following information about troubleshooting:

C.1 Verifying Requirements

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

C.2 What to Do if an Installation Error Occurs

If you encounter an error during installation:

C.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 records 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

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.

C.4 Silent or Noninteractive Installation Response File Error Handling

To determine whether a silent or nonintereactive 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:

Oracle Universal Installer or a configuration assistant validates the response file at runtime. If the validation fails, the 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 on interactive installation log files

C.5 Troubleshooting Configuration Assistants

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

C.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 cancelled -1

C.5.2 Fatal Errors

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

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

  2. Correct the cause of the fatal error.

  3. Reinstall the Oracle software.

C.6 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 Oracle Universal Installer to deinstall Oracle Database Client, manually remove the Oracle directory, and remove Oracle from the Registry Editor keys. Afterwards, reinstall the software.