A Troubleshooting the Oracle Database Companion CD Installation

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

A.2 X Window Display Errors

If you are running Oracle Universal Installer on a remote system and you want to display the user interface of the Oracle Universal Installer on your local system, then you may 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, then perform the following steps:

1. In a local terminal window, log in as the user that started the X Window session.

2. Enter the following command to enable the remote host to display X applications on the local X server:

   $ xhost fully_qualified_remote_host_name
   
   

   For example:

   $ xhost somehost.us.acme.com
   
   

3. 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 shell:

     % setenv DISPLAY workstation_name:0.0
     
     

4. To determine if X Window applications display correctly on the local system, enter the following command:

   $ xclock
   
   

   The X clock should appear on your monitor.

5. If the X clock appears, then close X clock and start Oracle Universal Installer again.

A.3 What to Do If an Installation Error Occurs

If you encounter an error during installation, then:

• Do not exit Oracle Universal Installer.

• If you clicked Next after you entered incorrect information on one of the installation screens, then 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, then refer to the "Reviewing the Log of an Installation Session" section.

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

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

A.4 Reviewing the Log of an Installation Session

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, then review the log file for information about possible causes of the problem.

To view the contents of the log file, follow these steps:

1. If necessary, enter the following command to determine the location of the oraInventory directory:

   $ cat /var/opt/oracle/oraInst.loc
   
   

   The inventory_loc parameter in this file specifies the location of the oraInventory directory.

2. Enter the following command to change directory to the Oracle Universal Installer log file directory, where orainventory_location is the location of the oraInventory directory:

   $ cd /orainventory_location/logs
   
   

3. 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:

   installActionsdate_time.log
   
   

4. To view the most recent entries in the log file, in which 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.

5. If the error displayed by Oracle Universal Installer or listed in the log file indicates a relinking problem, then refer to the following file for more information:

   $ORACLE_HOME/install/make.log
   

A.5 Troubleshooting Configuration Assistants

To troubleshoot an installation error that occurred when a configuration assistant was 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_HOME/cfgtoollogs directory. Try to fix the issue that caused the error.

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

oraInventory_location/logs/installActionsdate_time.log

A.6 Cleaning Up After a Failed Installation

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

1. Start Oracle Universal Installer as described in the "Installing Oracle Database 10g Products" section.

2. Click Deinstall Products on the Welcome screen, or click Installed Products on any Oracle Universal Installer screen.

   The Inventory screen appears, listing installed products.

3. Select the products that you want to remove, and then click Remove.

4. Manually remove the Oracle home directory created during the failed installation.

5. Reinstall the Oracle software.

A.7 Silent-Mode Response File Error Handling

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

/oraInventory_location/logs/silentInstalldate_time.log

If necessary, refer to the previous section 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

  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 response/stage.

• 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, 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.

A.8 Images Displayed Incorrectly in Oracle HTML DB

In the "Configuring Oracle HTTP Server for a New Oracle HTML DB Installation" section, you added an alias entry that points to the file system path where you copied the images directory. If images in Oracle HTML DB do not display correctly, then you may have more than one definition of the /i/ alias. To address this problem:

• If possible, rename the first instance of /i/ to a different alias name.

• Copy the images from the $ORACLE_HOME/htmldb/images directory to the directory defined by the first /i/ alias.

A.9 Oracle HTML DB Online Help Not Working

If users are accessing Oracle HTML DB through a virtual host, then the online Help will not work. Consider the following example:

The host name of the Oracle HTTP Server on which the Oracle HTML DB DAD resides is internal.server.com and the port is 7777. Users access Oracle HTML DB through a virtual host. In their Web browsers, users see external.server.com and the port 80.

In this example, Oracle HTML DB online Help will not work if the users cannot access internal.server.com. To resolve this issue, add the following lines to the Oracle HTML DB DAD to override the CGI environment variables SERVER_NAME and SERVER_PORT:

PlsqlCGIEnvironmentList SERVER_NAME=external.server.com
PlsqlCGIEnvironmentList SERVER_PORT=80