|Oracle® Enterprise Manager Administrator's Guide for Software and Server Provisioning and Patching
11g Release 1 (22.214.171.124.0)
|PDF · Mobi · ePub|
This appendix lists the log files you must review to resolve issues encountered while running a Deployment Procedure.
The following are OMS-related log files.
Generic EM Trace File
Provision Advisory Framework (PAF) Llogs
For Specific Deployment Procedure Instance
$<ORACLE_HOME>refers to the Oracle home of the OMS.
The following are Management Agent-related log files:
$<ORACLE_HOME>refers to the Oracle home of the Management Agent.
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.
On the OMS side:
Open the following file available in the Oracle home of the OMS:
@ log4j.rootCategory= parameter to
Restart the OMS by running the following commands:
$<ORACLE_HOME>/bin/emctl stop oms
$<ORACLE_HOME>/bin/emctl start oms
On the Management Agent side:
Open the following file available in the Oracle home of the Management Agent:
Make the following settings:
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.
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.
For Oracle Grid Infrastructure for standalone servers, the location is: