Skip Headers
Oracle® Database Installation Guide
11g Release 1 (11.1) for Linux

B32002-11
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

G Troubleshooting

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

G.1 Verify 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.

Read the Release Notes

Read the release notes for the product before installing it. The release notes are available on the Oracle Database 11g DVD. The latest version of the release notes is also available on the Oracle Technology Network Web site:

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

G.2 X Window Display Errors

If you run 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.
  1. In a local terminal window, log in as the user that started the X Window session.

  2. Enter the following command:

    $ xhost fully_qualified_remote_host_name
    

    For example:

    $ xhost somehost.us.example.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 whether 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, close the X clock and start Oracle Universal Installer again.

G.3 What to Do If an Installation Error Occurs?

If you encounter an error during installation:

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

Note:

If you run Oracle Universal Installer during the time that daily cron jobs run, then you may encounter unexplained installation problems if your cron job is performing cleanup, and temporary files are deleted before the installation is finished. Oracle recommends that you complete installation before daily cron jobs are run, or disable daily cron jobs that perform cleanup until after the installation is completed.

To view the log file, follow these steps:

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

    $ cat /etc/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 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, 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.

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

    $ORACLE_HOME/install/make.log
    

G.5 Troubleshooting Host Name Changes and CSS

If you change the host name for ASM, then the Oracle CSS daemon will not start. In order to counter this problem, please use the following steps:

For Example:

# $ORACLE_HOME/bin/localconfig [add] [delete] [ reset destination_Oracle_home ]
[-silent] [-paramfile Complete_path_of_file_specifying_parameter_values]

G.6 Troubleshooting Oracle Configuration Manager

This section lists some of the errors that may occur while using Oracle Configuration Manager and provides tips to troubleshoot these errors.

G.7 Troubleshooting Configuration Assistants

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

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

oraInventory_location/logs/installActionsdate_time.log

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

G.7.2 Fatal Errors

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

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

  2. Correct the cause of the irrecoverable error.

  3. Reinstall the Oracle software.

G.8 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 on fixing the issue.

G.9 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:

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.

G.10 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:

  1. Start Oracle Universal Installer as described in the "Installing the Oracle Database Software".

  2. Click Deinstall Products on the Welcome window or click Installed Products on any Installer window.

    The Inventory window appears, listing installed products.

  3. Select the Oracle home that contains the products that you want to remove, then click Remove.

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

  5. Reinstall the Oracle software.

To reinstall, you need to drop either one or two database schemas, depending upon the installation type.

G.11 After Failed Upgrade Installation

In the case of a failed upgrade installation, you need to revert Oracle Application Express to a earlier release and then remove the schemas associated with release 2.2. This section contains the following topics:

G.11.1 Reverting to Earlier Release

To revert to a previous Oracle Application Express release:

  1. If you altered the images directory, you need to point the text alias /i/ back to images directory for release 1.5.

  2. Run the following command in SQL*Plus:

    1. Start SQL*Plus and connect the database where Oracle Application Express is installed as SYS. For example:

      $ $ORACLE_HOME/bin/sqlplus 
      SQL> CONNECT SYS as SYSDBA
      Enter password: SYS_password
      
    2. To revert to Oracle Application Express release 1.5, execute the following:

      ALTER SESSION SET CURRENT_SCHEMA = FLOWS_010500;
      exec flows_010500.wwv_flow_upgrade.switch_schemas
      ('FLOWS_030000','FLOWS_010500');
      
    3. To revert to Oracle Application Express release 1.6, execute the following:

      ALTER SESSION SET CURRENT_SCHEMA = FLOWS_010600;
      exec flows_010600.wwv_flow_upgrade.switch_schemas
      ('FLOWS_030000','FLOWS_010600');
      
    4. To revert to Oracle Application Express release 2.0, execute the following:

      ALTER SESSION SET CURRENT_SCHEMA = FLOWS_020000;
      exec flows_020000.wwv_flow_upgrade.switch_schemas
      ('FLOWS_030000','FLOWS_020000');
      

To remove the release 2.2 schema:

  1. Start SQL*Plus and connect the database where Oracle Application Express is installed as SYS.

  2. Execute the following commands:

    DROP user FLOWS_030000 CASCADE;
    

G.11.2 After a Failed New Installation

To remove schemas after a failed new installation:

  1. Start SQL*Plus and connect the database where Oracle Application Express is installed as SYS.

  2. Run the following commands:

    drop user FLOWS_030000 cascade;
    drop user FLOWS_FILES cascade;
    

G.12 Images Displaying Incorrectly in Oracle Application Express

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

G.13 Online Help Not Working

If users are accessing Oracle Application Express through a Virtual Host, online Help will not work. Consider the following example:

In this example, Oracle Application Express online Help will not work if the users cannot access internal.server.com. To resolve this issue, add the following lines to the Oracle Application Express Database Access Descriptor (DAD) to override the CGI environment variables SERVER_NAME and SERVER_PORT:

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

See Also:

Oracle Application Server mod_plsql User's Guide for information on overriding the CGI environment variables.