G Troubleshooting the Oracle Database Installation

This appendix contains the following information about troubleshooting:

G.1 Verifying Requirements

Before you try any of the troubleshooting steps in this appendix, do the following:

G.2 Encountering Installation Errors

If you encounter an error during installation:

G.3 Reviewing the Log of an Installation Session

During an installation, Oracle Universal Installer records all 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. By default, the log files are located in the following directory:

SYSTEM_DRIVE:\Program Files\Oracle\Inventory\logs

Log filenames from interactive installations take the form:


For example, if an interactive installation occurred at 9:00:56 a.m. on October 14, 2005, the log file would be named:



Do not delete or manually alter the Inventory directory or its contents. Doing so can prevent Oracle Universal Installer from locating products that you install on your system.

G.4 Silent Mode Response File Error Handling

To determine whether a silent-mode installation succeeds or fails, check the silentInstallActionsdate_time.log file, located in DRIVE_LETTER:\Program Files\Oracle\Inventory\logs.

If necessary, see Section G.3, "Reviewing the Log of an Installation Session" for information about determining the location of the Inventory 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 a configuration assistant validates the response file at run time. If the validation fails, the silent-mode installation or configuration process ends.

See Also:

"Reviewing the Log of an Installation Session" for information about interactive installation log files

G.5 Troubleshooting Host Name Changes and CSS

If you change the host name for Oracle Automatic Storage Management, then the Oracle CSS service does not start. In order to solve this problem, use the following steps:

  1. Log in as a user with Administrator privileges.

  2. Run roothas.bat to deconfigure CSS.

    C:\> cd \app\oracle\product\12.1.0\grid\crs\install
    perl roothas.bat -deconfig -force


    Starting with Oracle Database 12c Release 1 (, the roothas.bat script replaces the roothas.pl script in the Oracle Grid Infrastructure home.

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

  3. Run gridconfig.bat script to reconfigure CSS using the new host name:

    C:\> cd \app\oracle\product\12.1.0\grid\crs\config
  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.

G.6 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_BASE\cfgtoollogs directory. Try to fix the issue that caused the error.


    Ensure that there is no space in the path.
  • If you see the "Fatal Error. Reinstall message", look for the cause of the problem by reviewing the log files. See "Irrecoverable Errors" for more information.

G.6.1 Configuration Assistant Failures

Oracle configuration assistant failures are noted at the bottom of the installation window. The configuration assistant interface displays additional information, if available. The configuration assistant execution status is stored in the installActionsdate_time.log file.

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.6.2 Irrecoverable Errors

If you receive an irrecoverable error while a configuration assistant is running:

  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.7 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 Windows and UNIX 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.

G.8 Troubleshooting Screen Display Issues

If you connect to Oracle database with the screen resolution 640 X 480 or 800 X 600, then the Next button in the GUI is not visible as it hides behind the Taskbar. In order to counter this problem, do one of the following:

  • Hide the Taskbar.

  • Move the Oracle Universal Installer screen up.

  • Set the screen resolution to 1024 X 768 or higher.

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.

Follow the instructions in "Removing Oracle Database Software" to run the Deinstallation tool.

G.10 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 an error 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 the Oracle Installation User for the Oracle home, and run the gridconfig.bat script located in the path Grid_home\crs\config.

  3. To complete the installation or upgrade, run the configToolAllCommands script, located in the path ORACLE_HOME\cfgtoollogs\configToolAllCommands.