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/technology/documentation/

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 /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 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, use the following steps:

  • Login as the root user

  • Run localconfig delete to deconfigure CSS. This will remove any configuration related files on the system that referenced the old host name.

  • Run localconfig add to reconfigure CSS using the new host name.

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.

  • Insufficient Privileges While Running installCCRSQL collectconfig

    When you run the installCCRSQL.sh script, it creates the ORACLE_OCM user and sets up a job to collect database configuration information. The ORACLE_OCM user requires EXECUTE privileges on UTL_FILE and DBMS_SCHEDULER for database versions 10g or later, and on the DBMS_JOB for pre-10g databases. If these privileges are granted to PUBLIC, the ORACLE_OCM user inherits these privileges, otherwise these privileges are explicitly granted when the installCCRSQL.sh script is executed. If the inherited privileges are revoked, the following errors indicating the lack of privileges will be logged in the alert_log:

    ORA-12012: error on auto execute of job 52
    ORA-04068: existing state of packages has been discarded
    ORA-04063: package body "ORACLE_OCM.package_name" has errors
    ORA-06508: PL/SQL: could not find program unit being called
    

    To resolve these errors, you must grant the missing EXECUTE privilege to the ORACLE_OCM user.

    • For database versions 10g and later, grant EXECUTE privileges on the UTL_FILE and DBMS_SCHEDULER packages to the ORACLE_OCM user by entering the following SQL*PLUS commands:

      SQL> grant execute on UTL_FILE to oracle_ocm;
      SQL> grant execute on DBMS_SCHEDULER to oracle_ocm;
      SQL> ALTER PACKAGE oracle_ocm.MGMT_DB_LL_METRICS compile;
      SQL> ALTER PACKAGE oracle_ocm.mgmt_config compile;
      
    • For pre-10g databases, grant EXECUTE privileges on the DBMS_JOB package to the ORACLE_OCM user by entering the following SQL*PLUS commands:

      SQL> grant execute on UTL_FILE to oracle_ocm;
      SQL> grant execute on DBMS_JOB to oracle_ocm;
      SQL> ALTER PACKAGE oracle_ocm.MGMT_DB_LL_METRICS compile;
      SQL> ALTER PACKAGE oracle_ocm.mgmt_config compile;
      
  • ORA-04021 Error

    There may be cases when the ORACLE_OCM user must be granted the required privileges during installation. While granting the privileges, the following error may occur in the $ORACLE_HOME/ccr/log/collectconfigSID.log:

    ORA-04021: timeout occurred while waiting to lock object SYS.<package like UTL_FILE>
    

    This error may occur if another procedure is using the package for which the privileges are being granted. To resolve this error, retry the install when the package is not being used. This error may occur while granting privileges on UTL_FILE, DBMS_SCHEDULER, or DBMS_JOB.

  • ORA-01925 Error While Running installCCRSQL

    This error may occur if the value of the MAX_ENABLED_ROLES initialization parameter has been exceeded. To resolve this error, you must increase the value of the MAX_ENABLED_ROLES parameter and restart the database as follows:

    1. Edit the initsid.ora file where sid is the database system identifier and increase the value of MAX_ENABLED_ROLES . If a server parameter (spfile) has been used, alter the MAX_ENABLED_ROLES parameter by using the following SQL*PLus command:

      SQL>alter system set MAX_ENABLED_ROLES=value scope=spfile

    2. Restart the database.

    Once the database has been restarted, re-run the installCCRSQL.sh script.

  • Incorrectly configured host names are displayed on My Oracle Support (formerly OracleMetaLink) with only the short names

    To ensure that host names are displayed with their fully qualified names on My Oracle Support (formerly OracleMetaLink), the /etc/hosts file must contain an entry that includes both the host name and the domain in the following format:

    IP-Address  Full-HostName  Short-HostName
    

    For example:

    10.10.10.10  myhost.mydomain  myhost
    

    If the /etc/hosts file has not been correctly configured, only the short name is displayed on My Oracle Support (formerly OracleMetaLink).

  • Oracle Configuration Manager Synchronization Messages: Oracle Configuration Manager does not allow you to run multiple commands simultaneously. If you attempt to do so, the following messages may be displayed:

    • Message: Another operation is in progress. Please wait...

      Description: There are several Oracle Configuration Manager commands that cannot run concurrently. If you try to run one of these commands while another command is in progress, the second command will not be executed until the first command is completed. A message indicating that another command is in progress is displayed. The second command will automatically be run when the first command is completed.

      Commands: emCCR collect, emCCR getupdates, emCCR update_components, and emCCR upload

      Action: Initially, take no action, the second command will be executed when the first command is completed. But if the command execution takes too long, a timeout will occur. If a timeout occurs, ensure there is no Oracle Configuration Manager activity by executing emCCR stop command. Delete the ccr/state/collector.lock file and restart the Scheduler by running the emCCR start command. If you run the command in Disconnected mode, ensure that no collection or update is taking place and then delete the ccr/state/collector.lock file.

    • Message: Operation blocked, waiting..

      Description: You cannot run the emCCR update_components command if any other emCCR command is running. If you try to run the command, it will be blocked. You also cannot run any emCCR command while emCCR update_components is running as all other commands will be blocked.

      Commands: configCCR and most of the emCCR commands

      Action: Initially, take no action, the command will get executed when the current command is completed. If a timeout occurs, ensure that there is no Oracle Configuration Manager activity by executing emCCR stop. Delete the ccr/state/semaphore.op* and ccr/state/semaphore.update* files, and restart Oracle Configuration Manager by running emCCR start. If running the command in Disconnected mode, ensure no collection or update is taking place and delete the ccr/state/semaphore.op* and the ccr/state/semaphore.update* files.

    • Message: The Scheduler is down for upgrade.

      Description: While upgrading Oracle Configuration Manager, you cannot run any of the emCCR commands.

      Commands: All emCCR commands

      Action: Retry the commands later.

G.7 Troubleshooting Configuration Assistants

To troubleshoot an installation error that occurs when a configuration assistant is 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, look for the cause of the problem by reviewing the log files. Refer to "Fatal Errors" for further instructions.

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

G.9 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 must drop either one or two database schemas, depending upon the installation type.

G.10 After Failed Upgrade Installation

In the case of a failed upgrade installation, you must 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.10.1 Reverting to Earlier Release

To revert to a previous Oracle Application Express release:

  1. If you altered the images directory, you must 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.10.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.11 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 multiple definitions of the /i/ alias. To address this issue:

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

  • Alternatively, copy the images from the $ORACLE_HOME/marvel/images directory to the directory defined by the first /i/ alias.

G.12 Online Help Not Working

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

  • The host name of the Oracle HTTP Server where the Oracle Application Express DAD resides is internal.server.com and the port is 7777.

  • Users access Oracle Application Express through a Virtual Host. In their Web browsers, users see external.server.com and port 80.

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 HTTP Server mod_plsql User's Guide for information on overriding the CGI environment variables.