Oracle® Enterprise Manager Advanced Configuration 10g Release 5 (10.2.0.5) Part Number E10954-03 |
|
|
PDF · Mobi · ePub |
When you install the Oracle Management Agent or the Oracle Management Service, Enterprise Manager automatically configures the system to save certain informational, warning, and error information to a set of log files.
Log files can help you troubleshoot potential problems with an Enterprise Manager installation. They provide detailed information about the actions performed by Enterprise Manager and whether or not any warnings or errors occurred.
This chapter not only helps you locate and review the contents of Enterprise Manager log files, but also includes instructions for configuring the log files to provide more detailed information to help in troubleshooting or to provide less detailed information to save disk space.
This chapter contains the following sections:
Locating and Configuring Management Agent Log and Trace Files
Locating and Configuring Management Service Log and Trace Files
The following sections provide information on the log and trace files for the Oracle Management Agent:
Controlling the Size and Number of Management Agent Log and Trace Files
Controlling the Size and Number of Fetchlet Log and Trace Files
Oracle Management Agent log and trace files store important information that support personnel can later use to troubleshoot problems. The Management Agent uses three types of log files:
The Management Agent log file (emagent.log
)
The Agent saves information to the log file when the Agent performs an action (such as starting, stopping, or connecting to a Management Service) or when the Agent generates an error (for example, when the Agent cannot connect to the Management Service).
The Management Agent trace file (emagent.trc
)
The Management Agent trace file provides an advanced method of troubleshooting that can provide support personnel with even more information about what actions the Agent was performing when a particular problem occurred.
The Management Agent startup log file (emagent.nohup
)
The Management Agent saves information to the startup log file when there is a problem starting the agent. This file is updated by the Management Agent Watchdog Process. When the Watchdog Process finds any problems, it logs to this file.
Following are other management agent log files:
Log File | Description |
---|---|
agabend.log |
This log provided in 10.2.0.3 or higher contains all the Agent startup errors. Errors will be added for each failed startup to this file. The Agent watchdog mines this file, to report on an abnormal end of the Agent. |
apmeum.log |
Log and trace information from the End-User monitoring (Chronos) scripts |
e2eme.log |
Log file for the End-To-End tracing of OC4J |
e2eme.trc |
Trace file for the End-To-End tracing of OC4J |
emagent.log |
Log file used by the Agent process. Contains all informational messages in local language. |
emagent.nohup |
Log file for the Agent watchdog. This will contain all actions the watchdog has performed. |
emagent.trc |
Trace file used by the Agent process. Contains all the trace messages in English only. |
emagent_memdump_<time>.trc |
Optional trace file, generated by an 'emctl status agent memory' command. Contains the overview of the memory usage of the Agent at that point in time. |
emagent_perl.trc |
Trace file for the PERL scripts. This includes the PERL metrics and the discovery |
emdctl.log |
Agent control utility log file |
emdctl.trc |
Agent control utility trace file |
emsubagent.log |
SNMP sub-Agent log file |
emsubagent.nohup |
SNMP sub-Agent log file with the STDOUT and STDERR messages. |
emsubagent.trc |
SNMP sub-Agent trace file |
nfsPatchPlug.log |
Log file for nfs agent during Oracle home patching. |
nmei.log |
Log file for the ilint XML file validation. |
nmei.trc |
Log file for the ilint XML file validation. |
nmo.trc |
Windows NT only. Trace with file additional authentication tracing is nmotracing is enabled in the emd.properties file. |
secure.log |
Log file with all secure operations done from the Agent. |
In addition, Enterprise Manager also provides a log file and a trace file for the fetchlets, which are software programs used by the Management Agent for certain data-gathering tasks:
emagentfetchlet.log
emagentfetchlet.trc
The log/trc files for the Agent are written in the Agent runtime directory. You can find the runtime directory by using this command:
$ emctl getemhome
The log and trace files will be located at <EMHOME>/sysman/log
.
See Also:
Chapter 1, "Introduction to Enterprise Manager Advanced Configuration" for information about locating the Agent home directory.Both the Management Agent log file and the Management Agent trace file are designed to increase in size over time as information is written to the files. However, they are also designed to reach a maximum size. When the files reach the predefined maximum size, the Management Agent renames (or rolls) the logging or trace information to a new file name and starts a new log or trace file. This process keeps the log files from growing too large.
To be sure you have access to important log or trace file information, the Management Agent will rollover the log and trace files four times by default. When it rolls the log or trace file over the fourth time, the Agent deletes the oldest rollover file.
As a result, you will often see a total of four log files and four trace files in the log directory. The following example shows three archived trace files and the current trace file in the AGENT_HOME/sysman/log
directory:
emagent.trc emagent.trc.1 emagent.trc.2 emagent.trc.3
You can control how large the log file and the trace file can get before the Management Agent creates a rollover file. You can also control how many rollover files are created before the Management Agent deletes any logging or tracing data.
To control the size and number of Management Agent Log and Trace Files:
Stop the Management Agent.
Locate the emd.properties
file, which is located in the following directory:
AGENT_HOME/sysman/config/ (UNIX) AGENT_HOME\sysman\config (Windows)
Use a text editor to open the emd.properties
file.
Use the information in Table 9-2 to locate and modify the Agent logging and tracing properties in the emd.properties
file.
Restart the Management Agent.
Table 9-2 Management Agent Log and Trace File Properties
To modify the amount of information saved in the Management Agent trace file:
Stop the Management Agent.
Locate the emd.properties
file, which is located in the following directory:
AGENT_HOME/sysman/config
Open the emd.properties
file using your favorite text editor and look for the following entries near the bottom of the file:
tracelevel.main=WARN tracelevel.emdSDK=WARN tracelevel.emdSDK.util=WARN tracelevel.ResMonitor=WARN tracelevel.Dispatcher=WARN tracelevel.ThreadPool=WARN tracelevel.pingManger=WARN . . .
Each of these properties controls the level of logging detail for the various subcomponents of the Management Agent.
Modify the amount of information that is included in the trace file by replacing the WARN value for each property to one of the values shown in Table 9-3.
Note:
The values described in Table 9-3 are case-sensitive.Restart the Management Agent.
Table 9-3 Enterprise Manager Component Tracing Levels
Level | Purpose |
---|---|
ERROR |
Include only critical errors in the trace file. This setting generates the least amount of tracing data. The trace file will likely grow at a relatively slow rate when you select this logging level. |
WARN |
Include warning information, in addition to critical errors. |
INFO |
Include informational messages, in addition to warning and critical error information. |
DEBUG |
Include debugging information, as well as informational tracing, warning, and critical errors. This setting generates the greatest amount of tracing data. Note: The trace file will likely grow at a relatively fast rate when you select this logging level. |
Like the Management Agent log and trace files, the Management Agent fetchlet log and trace files are designed to reach a maximum size before the Management Agent renames (or rolls) the information to a new file name and starts a new log or trace file.
To control the maximum size of the Management Agent fetchlet log and trace files, as well as the number of rollover files:
Stop the Management Agent.
Locate the emagentlogging.properties
file in the following directory:
AGENT_HOME/sysman/config
Open the emagentlogging.properties
file with a text editor and modify the entries described in Table 9-4.
Restart the Management Agent.
Table 9-4 Management Agent Servlet Log and Trace File Properties
Property | Purpose | Example |
---|---|---|
When the fetchlet log file reaches this size, the Management Agent copies the logging data to a new rollover file and creates a new |
log4j.appender. emagentlogAppender. MaxFileSize=20000000 |
|
This optional property indicates how many times the Management Agent will rollover the fetchlet log file to a new file name before deleting logging data. Note: Because the log file does not contain as much data as the trace file, it is usually not necessary to create more than one rollover file. As a result, this entry is not included in the properties file by default. |
log4j.appender.emagentlogAppender. MaxBackupIndex=1 |
|
When the fetchlet trace file reaches this size, the Management Agent copies the logging data to a new rollover file and creates a new |
log4j.appender. emagenttrcAppender. MaxFileSize=5000000 |
|
This property indicates how many times the Management Agent will rollover the trace file to a new file name before deleting tracing data. |
log4j.appender. emagenttrcAppender. MaxBackupIndex=10 |
By default, the Management Agent will save all critical and warning messages generated by the Management Agent fetchlets to the emagentfetchlet.trc
file. However, you can adjust the amount of logging information that the fetchlets generate.
To change the amount of tracing information generated by the Management Agent fetchlets:
Stop the Management Agent.
Locate the emagentlogging.properties
file in the following directory:
AGENT_HOME/sysman/config
Open the emagentlogging.properties
file with a text editor and locate the following entry:
log4j.rootCategory=WARN, emagentlogAppender, emagenttrcAppender
Change the value of the log4j.rootCategory
parameter to one of the values shown in Table 9-3.
Note:
The the values described in Table 9-3 are case-sensitive.Restart the Management Agent.
The following sections describe how to locate and configure the Management Service log files:
Controlling the Size and Number of Management Service Log and Trace Files
Controlling the Contents of the Management Service Trace File
Oracle Management Service log and trace files store important information that support personnel can later use to troubleshoot problems. The Management Service uses two types of log files:
The Management Service log file (emoms.log
)
The Oracle Management Service saves information to the log file when the Management Service performs an action (such as starting or stopping) or when the Management Service generates an error.
The Management Service trace file (emoms.trc
)
The Management Service trace file provides an advanced method of troubleshooting that can provide support personnel with even more information about what actions the Management Service was performing when a particular problem occurred.
The Management Service log and trace files are stored in the following directory inside the Oracle Application Server Home where the Oracle Management Service is installed and deployed:
AS_HOME/sysman/log/
The Management Service log and trace files increases in size over time as information is written to the files. However, the files are designed to reach a maximum size. When the files reach the predefined maximum size, the Management Service renames (or rolls) the logging information to a new file name and starts a new log or trace file. This process keeps the log and trace files from growing too large.
As a result, you will often see multiple log and trace files in the Management Service log directory. The following example shows one archived log file and the current log file in the AS_HOME/sysman/log
directory:
emoms.log emoms.log.1
To control the maximum size of the Management Service log and trace files, as well as the number of rollover files:
Stop the Management Service.
Locate the emomslogging.properties
file in the following directory:
AS_HOME/sysman/config
Open the emomslogging.properties
file with a text editor and modify the entries described in Table 9-5.
Restart the Management Service.
Table 9-5 Management Service Log File Properties in the emomslogging.properties File
Property | Purpose | Example |
---|---|---|
When the Management Service log file reaches this size, the Management Service copies the logging data to a new rollover file and creates a new |
log4j.appender.emlogAppender. MaxFileSize=20000000 |
|
This optional property indicates how many times the Management Service will rollover the log file to a new file name before deleting logging data. Note: Because the log file does not contain as much data as the trace file, it is usually not necessary to create more than one rollover file. As a result, this entry is not included in the properties file by default. |
log4j.appender.emlogAppender. MaxBackupIndex=1 |
|
When the Management Service trace file reaches this size, the Management Service copies the logging data to a new rollover file and creates a new |
log4j.appender.emtrcAppender. MaxFileSize=5000000 |
|
This property indicates how many times the Management Services will rollover the trace file to a new file name before deleting tracing data. |
log4j.appender.emtrcAppender. MaxBackupIndex=10 |
By default, the Management Service will save all critical and warning messages to the emoms.trc
file. However, you can adjust the amount of logging information that the Management Service generates.
To change the amount of logging information generated by the Management Service:
Stop the Management Service.
Locate the emomslogging.properties
file in the following directory:
AS_HOME/sysman/config
Open the emomslogging.properties
file with a text editor and locate the following entry:
log4j.rootCategory=WARN, emlogAppender, emtrcAppender
Modify the value of the log4j.rootCategory
parameter to one of the values shown in Table 9-3.
Note:
The values described in Table 9-3 are case-sensitive.Restart the Management Service.
The Management Service is a J2EE application running in an Oracle Application Server Containers for J2EE (OC4J) instance within the Application Server. Different components of the Application Server generate their own log files. These files contain important information that can be used later by support personnel to troubleshoot problems.
Table 9-6 lists the location of the log files for some components.
Table 9-6 Component Log File Location
Component | Location |
---|---|
HTTP Server |
ORACLE_HOME/Apache/Apache/logs/error_log.timeORACLE_HOME/Apache/Apache/logs/access_log.time |
OC4J |
ORACLE_HOME/j2ee/instance_name/logORACLE_HOME/j2ee/instance_name/application-deployments/application_name/application.log |
OPMN |
ORACLE_HOME/opmn/logs |
Web Cache |
ORACLE_HOME/webcache/logs |
The iAS files can only store upto 2 GB, so ensure that you either rotate the log files, or switch to ODL.
Refer to the Oracle Application Server Administrator's Guide for instructions on controlling the size and rotation of these log files.