I Troubleshooting

I.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 4.

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

I.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 any of these error messages, follow these steps:

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.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 if an X Window application displays 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.

   See Also:

   PC-X Server or operating system vendor documents for further assistance

I.3 Remote Terminal Installation Error

If you run the installation from a remote terminal, or if you use an su command to change users you might receive an error similar to the following:

Could not execute auto check for display colors using command
/usr/X11R6/bin/xdpyinfo

This can occur if the DISPLAY variable is not set, or the user running the installation is not authorized to open an X window. For instance, if you use an su command to change from a user that is authorized to open an X window to a user account that is not authorized to open an X window on the display, such as a lower-privileged user opening windows on the root user's console display.

To troubleshoot this issue, run the command echo $DISPLAY to ensure that the display variable is set to the correct visual or to the correct host. If the display variable is set correctly then either ensure that you are logged in as the user authorized to open an X window, or run the command xhost + to allow any user to open an X window.

I.4 What to Do If an Installation Error Occurs?

If you encounter an error during installation:

• Do not exit Oracle Universal Installer.

• If you click Next after you enter incorrect information on one of the installation screens, click Back to return to the screen and correct the information.

• If you encounter errors while Oracle Universal Installer is copying or linking files, then review the installation logs for more information.

  For copy file errors review:

  /u01/app/oraInventory/logs/timestamp for date of install.log
  /u01/app/oraInventory/logs/timestamp for date of install.err
  /u01/app/oraInventory/logs/timestamp for date of install.out
  

  For errors during linking review:

  $ORACLE_HOME/install/make.log
  

  If you encounter errors when you run the Oracle Universal Installer, then rerun the Oracle Universal Installer with the -debug option:

  $./runInstaller -debug
  

  Check the log file for details. Refer to "Reviewing the Log of an Installation Session" section.

• If you encounter an error while a configuration assistant is running, refer to "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.

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

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
   

   Run these commands to list 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 the time when the installation started:

   installActionsdate_time.log
   oraInstalldate_time.err
   oraInstalldate_time.out
   

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
   

I.6 Troubleshooting and Deconfiguring Oracle Restart

Running the roothas.sh command flags -deconfig -force enables you to deconfigure Oracle Restart without removing installed binaries. This feature is useful if you encounter an error during an Oracle Grid Infrastructure for a standalone server installation, when running the root.sh command, such as a missing operating system package. By running roothas.sh -deconfig -force you can deconfigure Oracle Restart, correct the cause of the error, and then run root.sh again.

To deconfigure Oracle Restart:

1. Log in as the root user.

2. Go to the Grid_home/crs/install directory. For example:

   # cd /u01/app/12.1.0/grid/crs/install
   

3. Run roothas.sh with the -deconfig -force flags. For example:

   # roothas.sh -deconfig -force
   

I.7 Troubleshooting Host Name Changes and CSS

If you change the host name for Oracle Automatic Storage Management (Oracle ASM), then the Oracle CSS daemon does not start. To solve this issue, perform the following steps:

1. Log in as the root user

2. Run roothas.sh to to deconfigure CSS:

   # cd /u01/app/oracle/product/12.1.0/grid/crs/install
   # perl roothas.sh -deconfig -force
   

   This removes any configuration on the system that referenced the old host name.

3. Run root.sh to reconfigure CSS using the new host name:

   # cd /u01/app/oracle/product/12.1.0/grid
   # ./root.sh
   

4. Go to the grid home's bin directory. Use the srvctl add database command with the -c SINGLE flag to add the database in an Oracle Restart configuration. Also use the srvctl add command to add the listener, the Oracle ASM instance, all Oracle ASM disk groups, and any database services to the Oracle Restart configuration.

   See Also:

   Oracle Database Administrator's Guide

I.8 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 "Irrecoverable Errors" for further instructions.

oraInventory_location/logs/installActionsdate_time.log

I.9 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 User's Guide for information about fixing the issue.

• Oracle home is cloned without completing the inventory steps.

• There is bad inventory.

• Inventory is not available but it is created when the Oracle Enterprise Manager Agent is installed in a separate Oracle home.

I.10 Troubleshooting Screen Display Issues

If you connect to Oracle database with a screen resolution of 640X480 or 800X600, then the Next button in the GUI is not visible as it hides behind the Taskbar. To fix this problem, perform one of the following:

• Hide the Taskbar.

• Move the Oracle Universal Installer screen up.

• Set the screen resolution to 1024X768 or higher.

I.11 Troubleshooting Memory Size Error

On Linux systems, if the operating system /dev/shm mount size is too small for the Oracle system global area (SGA) and program global area (PGA), it results in the following error:

ORA-00845: MEMORY_TARGET not supported on this system

Note that Memory Size (SGA and PGA), which sets the initialization parameter MEMORY_TARGET or MEMORY_MAX_TARGET, cannot be greater than the shared memory file system (/dev/shm) on your operating system.

The workaround, if you encounter the ORA-00845 error, is to increase the /dev/shm mountpoint size.

For example:

# mount -t tmpfs shmfs -o size=7g /dev/shm

To make this change persistent across system restarts, add an entry in /etc/fstab similar to the following:

shmfs /dev/shm tmpfs size=7g 0 0

I.12 Troubleshooting File Descriptors Error

If file descriptors are not sized correctly, you see an error from various Oracle processes and potentially a Linux Error EMFILE (Too many open files) error in non-Oracle processes:

ORA-27123: unable to attach to shared memory segment 

The workaround is that the number of file descriptors for each Oracle instance must be at least 512*PROCESSES. The number of descriptors for each process must be at least 512.

I.13 Silent-Mode Response File Error Handling

To determine if 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

• Oracle Universal Installer encounters an error, such as insufficient disk space

Oracle Universal Installer or configuration assistant validates the response file at runtime. If the validation fails, the silent-mode installation or configuration process ends.

I.14 Cleaning Up After a Failed Installation

If an installation fails, you must remove files that Oracle Universal Installer created during the attempted installation using the Deinstallation Tool.

For more information about how to run the Deinstallation Tool see Chapter 10, "Removing Oracle Database Software" and "Troubleshooting and Deconfiguring Oracle Restart"

I.15 Continuing Installations or Upgrades After Server Restarts

During an Oracle Grid Infrastructure for a standalone server installation or upgrade, the server might require a restart and you may see errors similar to the following:

ACFS-9427 Failed to unload ADVM/ACFS drivers. A system reboot is recommended
ACFS-9428 Failed to load ADVM/ACFS drivers. A system reboot is recommended

The workaround is to perform the following steps:

1. Restart the computer.

2. Log in as root, and run the orainstRoot.sh script. For example:

   $ sudo -s
   # cd /u01/app/oraInventory
   # ./orainstRoot.sh
   

3. Change directory to the Grid home and run the root.sh script. For example:

   # cd /u01/app/oracle/product/12.1.0/grid
   # ./root.sh
   

4. Configure a response file, and provide passwords for the installation. See "Postinstallation Configuration Using a Response File" for information about how to create the response file.

5. To complete the upgrade or installation, log in as the software installation owner and run the configToolAllCommands script, located in the path $ORACLE_HOME/cfgtoollogs/configToolAllCommands, specifying the response file that you created. For example, where the response file is gridinstall.rsp:

   $ cd $ORACLE_HOME/cfgtoollogs/configToolAllCommands
   $ ./configToolAllCommands RESPONSE_FILE=gridinstall.rsp