This appendix describes the log files that are created by the installer and Configuration Wizard.
Log files contain information that can help you troubleshoot problems with your installation or configuration.
This appendix contains the following sections:
By default, the installer writes logs files to the Oracle_Inventory_Location/log (on UNIX operating systems) or Oracle_Inventory_Location\logs (on Windows operating systems) directory. On UNIX operating systems, if you do not know the location of your Oracle Inventory directory, you can find it in the oraInst.loc file in the following directories (default locations):
Linux: /etc/oraInst.loc
HP-UX and Solaris: /var/opt/oracle/oraInst.loc
On Windows operating systems, the location for the inventory directory is %SystemDrive%\Program Files\Oracle\Inventory\logs. If you are using a 32-bit installer on a 64-bit Windows machine, the inventory directory is %SystemDrive%\Program Files (x86)\Oracle\Inventory\logs.
The following install log files are written to the log directory:
installdate-time-stamp.log
This is the main log file.
installdate-time-stamp.out
This log file contains the output and error streams during the installation.
installActionsdate-time-stamp.log
This file is used by the installer GUI to keep track of internal information.
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.log
This log file contains the output stream of the copy session.
oraInstalldate-time-stamp.err
This log file contains the error stream of the copy session.
To Change the Name of your Log File:
Use the -logFile parameter from the command line when you start the installer. For example:
java -jar fmw_infra_121200.jar -logFile C:\home\logs\my_custom_log_file.log
To Change the Logging Level for More or Less Verbose Logging:
Use the -logLevel parameter from the command line when you start the installer. For example:
java -jar fmw_infra_121200.jar -logLevel info
To Log Time Usage Information:
Use the -printtime parameter from the command line when you start the installer. Using the -printtime parameter creates the timeTakendate-time-stamp.log and timedate-time-stamp.log files in the same directory. For example:
java -jar fmw_infra_121200.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.
To Log Memory Usage Information:
Use the -printmemory parameter from the command line when you start the installer. For example:
java -jar fmw_infra_121200.jar -printmemory
The -printmemory parameter causes the memorydate-time-stamp.log to be created. This file contains memory usage information for the copy session.
To create a log file of your configuration session, start the Configuration Wizard with the -log option, as shown below:
On UNIX operating systems:
./config.sh -log=log_filename -log_priority=log_level
On Windows operating systems:
config.cmd -log=log_filename -log_priority=log_level
See Table E-1 for more details about the -log and -log_priority options.
Table E-1 Configuration Wizard Log File Options
| Parameter | Description |
|---|---|
|
|
Specify the location of your log file. If you specify an absolute path with your Other values that can be specified with
|
|
|
Specify the level of detail you want included in your logs. The acceptable values are listed below, from most detailed to least detailed:
|