Skip Headers
Oracle® Enterprise Manager Administrator's Guide for Software and Server Provisioning and Patching
11g Release 1 (11.1.0.1.0)

E16599-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

M Reviewing Log Files

This appendix lists the log files you must review to resolve issues encountered while running a Deployment Procedure.

OMS-Related Log Files

The following are OMS-related log files.

Note:

The $<ORACLE_HOME> refers to the Oracle home of the OMS.

Management Agent-Related Log Files

The following are Management Agent-related log files:

$<ORACLE_HOME>/sysma/logs/emagent.nohup

$<ORACLE_HOME>/sysma/logs/emagent.trc

Note:

The $<ORACLE_HOME> refers to the Oracle home of the Management Agent.

Advanced Options

Optionally, to capture more details, follow these steps to reset the log level and capture the logs mentioned in the previous sections.

Note:

Oracle recommends you to archive the old logs and have a fresh run after resetting the log level to capture the fresh logs.

If Installation or Cloning Steps Fail

The OUI/Clone steps generate installation and error log files, and since they are generated at runtime, their locations are printed in the job logs.

If Database Configuration Failed

Database Configuration Assistant generates a log file, and its location is printed in the job log.

As part of target discovery, we generate the newtargets.xml file where the newly provisioned targets are added. The following is the location. Here, $<ORACLE_HOME> refers to the Oracle home of the Management Agent.

$<ORACLE_HOME>/sysman/emd/newtargets.xml

For Oracle Grid Infrastructure for standalone servers, the location is:

$<ORACLE_HOME>/sysman/emd/hastargets.xml