H Troubleshooting

This appendix contains information about troubleshooting. It includes information about the following topics:

Section H.1, "Verifying Requirements"
Section H.2, "X Window Display Errors"
Section H.3, "Errors During Installation"
Section H.4, "Reviewing the Log of an Installation Session"
Section H.5, "Troubleshooting Configuration Assistants"
Section H.6, "Silent Response File Error Handling"
Section H.7, "Cleaning Up After a Failed Installation"

H.1 Verifying Requirements

Before performing any of the troubleshooting steps in this appendix, ensure that the system meets the requirements and that you have completed all of the preinstallation tasks specified in Chapter 2, "Preinstallation Tasks".

Read the Release Notes

Read the Release Notes for the product before installing it. The Release Notes are available on the Oracle Database DVD drive. The latest version of the Release Notes is also available on the Oracle Technology Network Web site at

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

H.2 X Window Display Errors

If you are running Oracle Universal Installer on a remote system and you want to display the Oracle Universal Installer user interface on a local system, you may see error messages similar to the following:

%DECW-E-CANT_OPEN_DISPL, Can't open display

If you see the preceding error message, and the X server is running on a UNIX host, then:

In a local terminal window, log in as the user that started the X Window session.
Enter the following command:
```
$ xhost +
```
Enter the following commands, where workstation_name is the host name or IP address of your workstation:
- Bourne, Bash, or Korn shell:
```
$ DISPLAY=workstation_name:0.0
$ export DISPLAY
```
- C or tcsh shell:
```
% setenv DISPLAY workstation_name:0.0
```
To determine whether X Window applications display correctly on the local system, enter the following command:
```
$ xclock
```
The X clock should be displayed on the monitor.
If the X clock is displayed, then close X clock and start Oracle Universal Installer again.

Note:

This procedure applies only to users of UNIX workstations. If you are using a PC or other system with X server software installed, refer to the X server documentation for information about how to permit remote systems to display X applications on the local system.

H.3 Errors During Installation

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 screens, click Back to return to the screen and correct the information.
If you encounter an error while Oracle Universal Installer is copying or linking files, refer to Section H.4, "Reviewing the Log of an Installation Session".
If you encounter an error while a configuration assistant is running, refer to Section H.5, "Troubleshooting Configuration Assistants".
If you cannot resolve the problem, remove the failed installation by following the steps listed in Section H.7, "Cleaning Up After a Failed Installation".

H.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.

To view the log file:

Determine the location of the oraInventory directory. This can be found as the value of the inventory_loc parameter in the ORAINST.LOC file, which is located in the hostname subdirectory of SYS$LOGIN.
Set default to the directory determined in step 1, and then to the LOGS subdirectory located there.
Obtain a directory listing to determine the file name of the log file. Installer log files have names similar to the following, where date_time indicates the date and time that the installation started:
```
INSTALLACTIONSdate_time.LOG
```
This command lists the files in the order of creation, with the most recent file shown last. Installer log files have names similar to the following, where date_time indicates the date and time that the installation started:
```
installActionsdate_time.log
```
If an error displayed by Oracle Universal Installer or listed in the log file indicates a relinking problem, refer to the following file for more information:
```
ORA_ROOT:[INSTALL]MAKE.LOG
```

H.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 H.4, "Reviewing the Log of an Installation Session".
Review the specific configuration assistant log file located in the ORA_ROOT:[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 Section H.5.2, "Fatal Errors" for further instructions.

H.5.1 Configuration Assistant Failure

Oracle configuration assistant failures are noted at the bottom of the installation screen. The configuration assistant interface displays additional information if available. The configuration assistant execution status is stored in the following file:

device:[orainventory_location.LOGS]SILENTINSTALLdate_time.LOG

The execution status codes are listed in Table H-1:

Table H-1 Execution Status Codes

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

H.5.2 Fatal Errors

If you receive a fatal error while a configuration assistant is running, you must remove the current installation and reinstall the Oracle software as follows:

Remove the failed installation as described in Section H.7, "Cleaning Up After a Failed Installation".
Correct the cause of the fatal error.
Reinstall the Oracle software.

H.6 Silent Response File Error Handling

To determine whether a silent installation succeeds or fails, refer to the following log file:

device:[orainventory_location.LOGS]SILENTINSTALLdate_time.LOG

If necessary, refer to the Section H.4, "Reviewing the Log of an Installation Session" for information about determining the location of the oraInventory 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 configuration assistant validates the response file at run time. If the validation fails, then the silent 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.

H.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. Perform the following steps to remove the files:

Start Oracle Universal Installer as described in Section 3.3.1, "Installing Oracle Database from the Hard Drive".
Click Deinstall Products on the Welcome screen or click Installed Products on any Installer screen.

The Inventory screen is displayed, listing installed products.
Select the Oracle home that contains the products that you want to remove, then click Remove.
Manually remove the Oracle home directory created during the failed installation.
Reinstall the Oracle software.