F Installation and Configuration Log File Locations
This appendix lists the locations of the various log files that are created during the prerequisites check, installation, and configuration phases of Enterprise Manager Grid Control components.
Enterprise Manager Grid Control Installation Log Files
During Enterprise Manager installation, the following log files are created:
Configuration Logs
lists the installation logs that are created.
Table F-1 Installation Log Files
Installation Type
Log File
Location
Enterprise Manager Using New Database
Enterprise Manager Using Existing Database
Additional Management Service
Additional Management Agent
Installation Logs
The installation action logs that are created will provide complete information on the installation status. This log is located at the following locations:
The installActions log file is located in the oraInventory directory by default. This log file will be copied on to the above-mentioned Oracle home location after the installation is complete.
Repository and Secure Logs
The repository and secure logs are located in the Management Service Oracle home for the following installation types:
Enterprise Manager Using a New Database
Enterprise Manager Using an Existing Database
Additional Management Service
Repository Log Location
The repository log is located at:
In the above-mentioned path, the emrepmgr will be the SID .
Secure Log Location
The secure log is located at:
If you are installing an additional Management Agent, the secure log is located at:
Agent Deploy Log Files
The following agent prerequisite check and installation logs are available at these locations:
Connectivity Logs: the following connectivity logs for the local node will be available at the following locations:
Table F-2 Connectivity Log Locations
Log File
Location
Prerequisite Logs: The following prerequisite logs for will be available at the following locations:
Table F-3 Prerequisite Log Locations
Log File
Location
The time stamp in the log files of prereq/install/upgrade function may not be the same as the time-stamp in the $OMS_HOME/sysman/prov/agentpush/ / . These time stamps can differ considerably from the OMS host because these logs are generated in remote nodes and are collected back to OMS after the agent installation or upgrade.
Table F-4 lists all the other installation logs that are created during an agent installation using Agent Deploy.
Table F-4 Installation Logs Created During Agent Installation Using Agent Deploy
Logs
Location
Description
Agent Deploy application logs.
Logs of the remote interfaces layer.
Log or error of the new agent installation or new cluster agent installation.
Log or error of the upgrade operation using Agent Deploy
Log or error of the agent installation using the Shared Agent Home option in Agent Deploy.
Log or error of the cluster upgrade operation using Agent Deploy.
Log or error of the config operation in case of upgrade on a shared cluster.
Log or error of the configuration of shared cluster in case of an agent installation on a shared cluster.
Log/error of the running of preinstallation script, if specified.
Log/error of running of root.sh .
Log or error of running of postinstallation script, if specified.
installActions .log , oraInstall .err/.out
Logs of Oracle Universal Installer.
Status of agent after running emctl status agent from the agent home.
L Installation and Configuration Log Files
This appendix lists the locations of the various log files that are created during the prerequisites check, installation, and configuration phases of Enterprise Manager Grid Control components.
In particular, this appendix covers the following:
Enterprise Manager Grid Control Installation Logs
This section describes the following log files that are created while installing Enterprise Manager Grid Control:
Installation Logs
The following are the installation logs, which provide complete information on the installation status:
The installActions log file is located in the oraInventory directory by default. This log file will be copied on to the above-mentioned Oracle home location after the installation is complete.
Configuration Logs
This section describes the following configuration logs:
General Configuration Logs
The Oracle Management Service (OMS) configuration logs are located in the following location of the Oracle home of the OMS.
Table L-1 lists the configuration logs for different installation types.
Table L-1 General Configuration Logs
Installation Type
Location
Install a new Enterprise Manager system
Note: refers to the Oracle home of the OMS.
Add an additional Management Service
Note: refers to the Oracle home of the OMS.
Install Oracle Management Agent
Note: refers to the Oracle home of the Management Agent.
Repository Configuration Logs
This section describes the following repository configuration logs:
SYSMAN Schema Operation Logs
The SYSMAN schema operation logs are available in the following location of the Oracle home of the OMS. Listed in this directory is an overall log file, emschema.log , which logs all the actions performed by all the instances of RepManager run.
In this location, for each run of RepManager, a new subdirectory is created based on the time at which the RepManager was run.
For example, if the RepManager was run and an instance was created at 09/29/2007 12:50PM, then the following subdirectory is created.
An instance of RepManager ( or equivalently RepManager) can have multiple schema actions, mainly CREATE, DROP, UPGRADE, TRANSX, and RESUME_RETRY. For each action, a subdirectory is created.
For example, if a CREATE action is performed by a RepManager instance at 09/29/2006 12:51PM, then the following subdirectory is created. Listed under this subdirectory are RCU-related log files and emschema.log.CREATE log file that logs the CREATE action-specific messages.
In general, in $ /sysman/log/schemananager/m_ /m_ . , the following files are created:
If the any of the schema operations (CREATE/UPGRADE/PREUPGRADE/DROP) fail in SQL execution, and if you retry the operation by clicking Retry , then a separate subdirectory titled m_ .RESUME_RETRY is created.
The following shows the overall directory structure of repository operation logs for different schema actions:
MDS Schema Operation Logs
MDS Schema Creation Log
For MDS schema creation operation, the following log is available in the Oracle home of the OMS:
For more information, review the following logs from the Oracle home of the OMS:
For MDS schema drop operation, the following logs are available in the location you specified by using the -logDir argument while invoking the MDS schema drop command:
However, if you did not specify any custom location while invoking the MDS schema drop command, then the logs are created in the Oracle home of the OMS. For example, /scratch/OracleHomes/oms11g/mds.log and /scratch/OracleHomes/oms11g/emmdsdrop_ .log .
Secure Logs
For OMS, the following secure log is available in the OMS Instance Base location. Here, , for example, can be EMGC_OMS1 .
For Management Agents, the following secure log is available in the Oracle home of the Management Agent.
Oracle Management Service Logs
The following log files that provide information about the running OMS are available in the OMS Instance Base location. Here, , for example, can be EMGC_OMS1 .
Agent Deployment Log Files
This section describes the locations for the following agent deployment log files:
Connectivity Logs
Table L-2 lists the connectivity logs for the local node and their locations. Note that mentioned in this table refer to the Oracle home of the OMS.
F Troubleshooting the Oracle Database Installation
This appendix contains the following information about troubleshooting:
F.1 Verifying Requirements
Before you try any of the troubleshooting steps in this appendix, do the following:
Check Chapter 2, «Oracle Database Preinstallation Requirements» to ensure that the system meets the requirements and that you have completed all of the preinstallation tasks.
Read the release notes for the product on your platform before installing it. The release notes are available on the Oracle Database installation media. You can find the latest version of the release notes on the Oracle Technology Network Web site:
F.2 Encountering Installation Errors
If you encounter an error during installation:
Do not exit Oracle Universal Installer.
If you clicked Next after you entered incorrect information about one of the installation windows, click Back to return to the window and correct the information.
If you encounter an error while Oracle Universal Installer is copying or linking files, see «Reviewing the Log of an Installation Session» for interactive installations or «Silent or Noninteractive Installation Response File Error Handling» for more information.
If you encounter an error while a configuration assistant is running, see the «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.
F.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:
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.
F.4 Silent or Noninteractive Installation Response File Error Handling
To determine whether a silent or noninteractive installation succeeds or fails, check the silentInstallActions date_time .log file, located in DRIVE_LETTER :\Program Files\Oracle\Inventory\logs .
If necessary, see the previous section for information about determining the location of the Inventory directory.
A silent or noninteractive 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 ensure that it points to the products.xml file in the installation media. In the installation media, this products.xml is in database\stage .
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 or noninteractive 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.
«Reviewing the Log of an Installation Session» for information about interactive installation log files
F.5 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 \ ORACLE_HOME \cfgtoollogs directory. Try to fix the issue that caused the error.
If you see the Irrecoverable Error. Reinstall message, look for the cause of the problem by reviewing the log files. See «Irrecoverable Errors» for more information.
F.5.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 installActions date_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
F.5.2 Irrecoverable Errors
If you receive an irrecoverable error while a configuration assistant is running:
Remove the failed installation as described in the «Cleaning Up After a Failed Installation» section.
Correct the cause of the irrecoverable error.
Reinstall the Oracle software.
F.6 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 Chapter 6, «Removing Oracle Database Software» to run Oracle Universal Installer to deinstall Oracle Database, manually remove the Oracle directory, and remove Oracle from the Registry Editor keys. Later, reinstall the software.
