Troubleshooting Your Installation

E Troubleshooting Your Installation

You might encounter issues while installing or deinstalling your Oracle Fusion Middleware product. Review this information to help you troubleshoot those issues.

Configuring Installation and Configuration Log Files
Log files created by the Installer and Configuration Wizard contain information that can help you troubleshoot problems with your installation or configuration.
Specifying a Custom Temporary Directory
The installation program uses a temporary directory for extracting the files that are needed to install the software on the target system. If the default temporary directory (for example, /var/tmp) used by the installation program doesn’t have enough free memory when you run the installer, the installer fails to start.

Configuring Installation and Configuration Log Files

Log files created by the Installer and Configuration Wizard contain information that can help you troubleshoot problems with your installation or configuration.

Installation Log Files
By default, the installer writes logs files to the Central_Inventory_Location/log (on UNIX operating systems) or Central_Inventory_Location\logs (on Windows operating systems) directory.
Configuration Log Files
To create a log file of your configuration session, start the Configuration Wizard with the -log option.

Parent topic: Troubleshooting Your Installation

Installation Log Files

By default, the installer writes logs files to the Central_Inventory_Location/log (on UNIX operating systems) or Central_Inventory_Location\logs (on Windows operating systems) directory.

On UNIX operating systems, if you do not know the location of your Oracle central inventory, you can find it in the oraInst.loc file in the following directories (default locations):

Linux: /etc/oraInst.loc
HP-UX, IBM AIX, Mac OS X, and Solaris: /var/opt/oracle/oraInst.loc

On Windows operating systems, the location for the central inventory directory is %SystemDrive%\Program Files\Oracle\Inventory\logs.

The following install log files are written to the log directory:

installdate-time-stamp.log

This is the main log file.
installProfiledate-time-stamp.log

This log file contains the overall statistics like time taken to complete the installation, as well as configuration, memory, and CPU details.
oraInstalldate-time-stamp.out

This log file contains additional log output.
oraInstalldate-time-stamp.err

This log file contains additional log output.

Patch-related log files created by the Auto Updates feature are written to the ORACLE_HOME/cfgtoollogs directory.

To Change the Logging Level for More or Less Verbose Logging:

Use the -logLevel option from the command line when you start the installer. For example:

java -jar fmw_12.2.1.3.0_infrastructure_generic.jar  -logLevel finer

To Log Time Usage Information:

Use the -printtime option from the command line when you start the installer. The -printtime option creates the timetimestamp.log file, which contains information about the time taken to perform various elements of the requested Oracle Universal Installer operation (such as -install). For example:

java -jar fmw_12.2.1.3.0_infrastructure_generic.jar  -printtime

Below is a brief description of the timeTakendate-time-stamp.log and timedate-time-stamp.log files:

timeTakendate-time-stamp.log

This file contains information for the amount of time taken to move between screens (applicable for GUI installations only).
timedate-time-stamp.log

This file contains time information for the copy session.

Parent topic: Configuring Installation and Configuration Log Files

Configuration Log Files

To create a log file of your configuration session, start the Configuration Wizard with the -log option.

On UNIX operating systems:

ORACLE_HOME/oracle_common/common/bin/config.sh -log=log_filename -log_priority=log_level

On Windows operating systems:

ORACLE_HOME\oracle_common\common\bin\config.cmd -log=log_filename -log_priority=log_level

See the following table for more details about the -log and -log_priority options.

Table E-1 Configuration Wizard Log File Options

Option Description

Option	Description
`-log`	Specify the location of your log file. If you specify an absolute path with your `log_filename`, then your log file is created there. If you only specify a file name with no path, then the log files are created in the `logs` directory in the Oracle home. Other values that can be specified with `-log` are: `stdout` This writes the error message to the standard output stream. `stderr` This writes the error messages to the standard error stream. `disable` This disables default logging so that no log files are generated in `ORACLE_HOME/logs` (on UNIX operating systems) or `ORACLE_HOME\logs` (on Windows operating systems).
`-log_priority`	Specify the level of detail you want included in your logs. The acceptable values are listed, from most detailed to least detailed: `debug` `info` `warning` `error` `fatal`

-log

Specify the location of your log file.

If you specify an absolute path with your log_filename, then your log file is created there. If you only specify a file name with no path, then the log files are created in the logs directory in the Oracle home.

Other values that can be specified with -log are:

stdout

This writes the error message to the standard output stream.
stderr

This writes the error messages to the standard error stream.
disable

This disables default logging so that no log files are generated in ORACLE_HOME/logs (on UNIX operating systems) or ORACLE_HOME\logs (on Windows operating systems).

-log_priority

Specify the level of detail you want included in your logs.

The acceptable values are listed, from most detailed to least detailed:

debug
info
warning
error
fatal

Parent topic: Configuring Installation and Configuration Log Files

Specifying a Custom Temporary Directory

The installation program uses a temporary directory for extracting the files that are needed to install the software on the target system. If the default temporary directory (for example, /var/tmp) used by the installation program doesn’t have enough free memory when you run the installer, the installer fails to start.

As a result, if the temporary directory used by the installation program doesn’t have adequate space, you must clear up space in this directory before you can install your Fusion Middleware product.

Alternatively, you can also specify a custom temporary directory to use when you run the installer by doing one of the following:

If you are installing a generic (.jar) distribution, then specify the -Djava.io.tmpdir=tmp_dir_path option on the command line when you start the installation program. Replace tmp_dir_path with the full path of the directory you want to designate as a temporary storage area for the installation program.

For example, if you want to use /scratch/temp as the temporary directory for installing Oracle Fusion Middleware Infrastructure on Linux, you can start the installer by running the following command:
```
java -Djava.io.tmpdir=/scratch/temp -jar fmw_12.2.1.3.0_infrastructure_generic.jar 
```
If you are installing a platform-specific (.bin) distribution, then specify the -J-Djava.io.tmpdir=tmp_dir_path option on the command line when you start the installation program. Replace tmp_dir_path with the full path of the directory you want to designate as a temporary storage area for the installation program.

For example, if you want to use /scratch/temp as the temporary directory for installing Oracle HTTP Server on Linux, you can start the installer by running the following command:
```
./fmw_12.2.1.3.0_ohs_linux64.bin -J-Djava.io.tmpdir=/scratch/temp
```

Parent topic: Troubleshooting Your Installation