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.
Read the release notes for the product before installing it. The release notes are available on the Oracle Database 10g disc. The latest version of the release notes is also available on the Oracle Technology Network Web site:
If you are running Oracle Universal Installer on a remote system and you want to display Oracle Universal Installer's user interface on your local system, you might see error messages similar to the following:
"Failed to connect to server" "Connection refused by server" "Can't open display"
If you see one of these error messages, follow these steps:
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.
In a local terminal window, log in as the user that started the X Window session.
Enter the following command:
$ xhost fully_qualified_remote_host_name
$ xhost somehost.us.acme.com
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
% setenv DISPLAY workstation_name:0.0
To determine whether X Window applications display correctly on the local system, enter the following command:
The X clock should appear on your monitor.
If the X clock appears, close the X clock and start Oracle Universal Installer again.
You can use both raw character devices and block devices as raw volumes in creating a database. Because block devices are supported, the kernel level limitation on the maximum number of raw devices is removed and you can configure additional raw volumes to meet your requirements.
If you encounter an error during installation:
Do not exit Oracle Universal Installer.
If you clicked Next after you entered incorrect information on 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 the "Reviewing the Log of an Installation Session" section.
If you encounter an error while a configuration assistant is running, refer to 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.
During an installation, Oracle Universal Installer records all of 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, follow these steps:
If necessary, enter the following command to determine the location of the
inventory_loc parameter in this file specifies the location of the
Enter the following command to change directory to Oracle Universal Installer log file directory, where
orainventory_location is the location of the
$ cd /orainventory_location/logs
Enter the following command to determine the name of the log file:
$ ls -ltr
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:
To view the most recent entries in the log file, where information about a problem is most likely to appear, enter a command similar to the following:
$ tail -50 installActionsdate_time.log | more
This command displays the last 50 lines in the log file.
If the error displayed by Oracle Universal Installer or listed in the log file indicates a relinking problem, refer to the following file for more information:
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_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 the "Fatal Errors" section for further instructions.
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:
The execution status codes are listed in the following table:
|Configuration assistant succeeded||0|
|Configuration assistant failed||1|
|Configuration assistant cancelled||-1|
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 the "Cleaning Up After a Failed Installation" section.
Correct the cause of the fatal error.
Reinstall the Oracle software.
To determine whether a silent-mode installation succeeds or fails, refer to the following log file:
If necessary, refer to the previous section for information about determining the location of the
A silent 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 filled out correctly, the staging area location may be incorrect. If this is the case, check the
FROM_LOCATION variable and make sure that it points to the
products.xml file in the installation media. In the installation media, this
products.xml is in
Oracle Universal Installer encounters an error or any prerequisite checks fail, such as insufficient disk space
Oracle Universal Installer or configuration assistant validates the response file at run time. If the validation fails, the silent-mode 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.
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 the "Installing the Oracle Database Software" section.
Click Deinstall Products on the Welcome window or click Installed Products on any Installer window.
The Inventory window appears, 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.