| Oracle® Enterprise Manager Advanced Configur
ation 10g Release 1 (10.1) Part Number B12013-01 |
|
|
View PDF |
When you install the Oracle Management Agent or the Oracle Management Service, Enterprise Manager automatically configures the system to save certain informational, warnin g, and error information to a set of log files.
Log files can help you troubleshoot potential problems with an Enterprise Mana ger 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 les s detailed information to save disk space.
This chapter contains the following sections:
Locating and Configuring Management Agent Log and Trace Files
Locati ng 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 fi les 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 i nformation about what actions the Agent was performing when a particular problem occurred.
The Managemen
t Agent startup log file (emagent.nohup)
The Management Agent saves inform ation to the startup log file when there is a problem starting the agent. This file is updated by the Management Agent Watchdog Proce ss. When the Watchdog Process logs any problems it finds to this file.
In addition, Enterprise Manager also provides a lo g 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 Management Agent log files are stored in the following directory when you install the Management Agent:
AGENT_HOME/sysman/log/
|
See Also: Chapter 1, " Introduction to Enterprise Manager Advanced Configuration " for info rmation about locating the Agent home directory. |
Both the Management Agent log file and the Management Agent trace file ar e designed to increase in size over time as information is written to the files. However, they are also designed to reach a maximum s ize. 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 o
ften 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 f iles 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 op
en the emd.properties file.
Use the information in Table 5-1 to locate and modi
fy the Agent logging and tracing properties in the emd.properties file.
Restart the Management Agent. p>
| Property | Purpose | Example |
|---|---|---|
LogFilewithPID |
When set to TRUE, this property appends the process ID of the Management Agent to the log file name. This makes it easier to identify the process ID of the Management Agent you are monitoring. | LogFilewithPID=true |
|
|
When the Agent log file reaches this si
ze (in kilobytes), the Management Agent copies the logging data to a new rollover file and creates a new emagent.log log
ging file. |
LogFileMaxSize=4096 |
LogFileMaxRolls |
By the default, the Agent will rollover t he log file four times before it deletes any logging data. The number of rollover files is controlled by this property. | LogFileMaxRolls=4 |
TrcFileMaxSize |
When the Agent trace file reach this size (in kilobytes), the Manage
ment Agent copies the logging data to a new rollover file and creates a new emagent.trc logging file. |
TrcFileMaxSize=4096 |
| TrcFileMaxRolls | By the default, the Agent will rollover the trace file four times before it deletes any tracing data. The number of ro llover files is controlled by this property. | TrcFileMaxRolls=4 |
|
< font face="arial, helvetica, sans-serif">See Also: "Starting, Stopping, and Checking the Status of the Management Agent on UNIX" |
Locate the emd.properties file, which is located in the following directory:
< em>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=W ARN . . .
Each of these properties controls the level of logging detail for the various subcomponents of the Management A gent.
Modify the amount of information that is included in the trace file by replacing the WARN value for each prope rty to one of the values shown in Table 5-2.
Restart the Management Agent.
Table 5-2 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 sl ow rate when you select this logging level. |
| WARN | Include warning information, in addition to critical errors. |
| INFO | Include in formational messages, in addition to warning and critical error information. |
| DEBUG | Include debugging information, as well as info
rmational 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 trac e 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.
< !-- class="inftblNoteAlso -->Locate the emagentlogging.properties file in the following directory:
AGENT_HOME/sysman/config
Open the emagentl
ogging.properties file with a text editor and modify the entries described in Table 5-3.
Restart the Management Agent.
Table 5-3 Management Agent Servlet Log and Trace File Pr operties
By default, the Management Agent will save all critical and warning messages generated by the Management Agen
t fetchlets to the emagentfetchlet.trc file. However, you can adjust the amount of logging information that the fetchlet
s generate.
To change the amount of tracing information generated by the Management Agent fetchlets:
Stop the Management Agent.
Locate the emagentlogging.properties file in t
he following directory:
AGENT_HOME/sysman/config
Open the emagentlogging.pr
operties 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 5-2.
Restart the M anagement Agent.
The following sections describe how to locate and con figure the Management Service log files:
Controlling the Size and Number of Management Service Log and Trace Fil es
Controlling the Contents of the Management Service Trace File
Orac le Management Service log and trace files store important information that support personnel can later use to troubleshoot problems. The Management Service uses three types of log files:
The Management Service log file (emoms.log)
The Oracle Management Service saves information to the log file when the Managem ent 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 Serv ice trace file provides an advanced method of troubleshooting that can provide support personnel with even more information about wha t 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 Se rvice log and trace files increases in size over time as information is written to the files. However, the files are designed to reac h 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 ar
chived 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 file s, as well as the number of rollover files:
Stop the Management Service.
Locate the emomslogging.properties file in the following directory:
AS_HO ME/sysman/config
Open the emomslogging.properties file with a text editor and modify the entries d
escribed in Table 5-4.
Restart the Management Service.
Table 5-4 Management Service Log File Properties in the emomslogging.properties File
By de
fault, 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 generate d by the Management Service:
Stop the Management Service.
Locate the emomslogging.propert
ies file in the following directory:
AS_HOME/sysman/config
Open the
emomslogging.properties file with a text editor and locate the following entry:
Modify the value of the log4j.rootCategory parameter to one of the values shown in Table 5-2.
Restart the Management Service.