11 Locating and Configuring Enterprise Manager Log Files

About the Management Agent Log and Trace Files

Oracle Management Agent log and trace files store important information that support personnel can later use to troubleshoot problems. The OMA uses three types of log files:

• Oracle 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 an OMS) or when the Agent generates an error (for example, when the Agent cannot connect to an Oracle Management Service).

• Oracle 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.

• Oracle Management Agent startup log file (emagent.nohup)

  The Watchdog Process saves information about the agent into the startup log file when the agent starts or stops (normally or abnormally). The support personnel use this log file to get information about other associated files when an agent abnormally stops.

Following are other management agent log files:

Locating the Management Agent Log and Trace Files

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.

About Management Agent Rollover Files

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

Controlling the Size and Number of Management Agent Log and Trace Files

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:

1. Stop the Management Agent.

2. Locate the emd.properties file, which is located in the following directory:

   AGENT_HOME/sysman/config/ (UNIX)
   AGENT_HOME\sysman\config (Windows)
   

   Note:

   For Clustered Agent installation, the emd.properties file is located in the following directory:

   AGENT_HOME/<node>/sysman/config
   

3. Use a text editor to open the emd.properties file.

4. Use the information in Table 11-2 to locate and modify the Agent logging and tracing properties in the emd.properties file.

5. Restart the Management Agent.

LogFilewithPID

LogFileMaxSize

LogFileMaxRolls

TrcFileMaxSize

Controlling the Contents of the Management Agent Trace File

To modify the amount of information saved in the Management Agent trace file:

1. Stop the Management Agent.

2. Locate the emd.properties file, which is located in the following directory:

   AGENT_HOME/sysman/config/ (UNIX)
   AGENT_HOME\sysman\config (Windows)
   

   Note:

   For Clustered Agent installation, the emd.properties file is located in the following directory:

   AGENT_HOME/<node>/sysman/config
   

3. 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.

4. 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 11-3.

   Note:

   The values described in Table 11-3 are case-sensitive.

5. Restart the Management Agent.

Controlling the Size and Number of Fetchlet Log and Trace Files

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:

1. Stop the Management Agent.

2. Locate the emagentlogging.properties file in the following directory:

   AGENT_HOME/sysman/config/ (UNIX)
   AGENT_HOME\sysman\config (Windows)
   

   Note:

   For Clustered Agent installation, the emd.properties file is located in the following directory:

   AGENT_HOME/<node>/sysman/config
   

3. Open the emagentlogging.properties file with a text editor and modify the entries described in Table 11-4.

4. Restart the Management Agent.

Controlling the Contents of the Fetchlet Trace File

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:

1. Stop the Management Agent.

2. Locate the emagentlogging.properties file in the following directory:

   AGENT_HOME/sysman/config/ (UNIX)
   AGENT_HOME\sysman\config (Windows)
   

   Note:

   For Clustered Agent installation, the emd.properties file is located in the following directory:

   AGENT_HOME/<node>/sysman/config
   

3. Open the emagentlogging.properties file with a text editor and locate the following entry:

   log4j.rootCategory=WARN, emagentlogAppender, emagenttrcAppender
   

4. Change the value of the log4j.rootCategory parameter to one of the values shown in Table 11-3.

   Note:

   The the values described in Table 11-3 are case-sensitive.

5. Restart the Management Agent.

About the Oracle Management Service Log and Trace Files

OMS log and trace files store important information that support personnel can later use to troubleshoot problems. OMS uses the following six types of log files:

• Oracle Management Service log file (emoms.log)

  OMS saves information to the log file when it performs an action (such as starting or stopping) or when it generates an error.

• Enterprise Manager Control log file (emctl.log)

  The information is saved to emctl.log file, when you run the Enterprise Manager Control commands.

• Oracle Management Service trace file (emoms.trc)

  OMS trace file provides an advanced method of troubleshooting that can provide support personnel with even more information about what actions the OMS was performing when a particular problem occurred.

• Oracle Management Service Message file (emctl.msg)

  OMS saves troubleshooting messages to the file when OMS restarts itself after a critical error.

• Virtualization Management pack log file (emovm.log)

  The errors generated during the virtualization of an Enterprise Manager is saved into the emovm log file.

• Virtualization Management Pack trace file (emovm.trc)

  The Virtualization Management Pack trace file provides an advanced method of troubleshooting. Support personnel can use them for debugging the errors related to virtualization operation of an Enterprise Manager.

Locating Oracle Management Service Log and Trace Files

OMS log and trace files are stored in the following location:

<EM_INSTANCE_BASE>/em/<OMS_NAME>/sysman/log/

Where, <EM_INSTANCE_BASE> is the OMS Instance Base directory. By default, the OMS Instance Base directory is gc_inst, which is present under the parent directory of the Oracle Middleware Home.

For example, if the Oracle Middleware Home is /u01/app/Oracle/Middleware, then the instance base directory is /u01/app/Oracle/gc_inst, and the log and trace files are available in /u01/app/Oracle/gc_inst/em/EMGC_OMS1/sysman/log/ directory path.

Controlling the Size and Number of Oracle Management Service Log and Trace Files

OMS 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 OMS 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 OMS log directory. The following example shows one archived log file and the current log file in the /u01/app/Oracle/gc_inst/em/EMGC_OMS1/sysman/log/ directory:

emoms.log
emoms.log.1

To control the maximum size of the OMS log and OMS trace files, as well as the number of rollover files, run the following command, and specify details as described in Table 11-5:

emctl set property -name <property> -value <property value> -module logging

Controlling the Contents of the Oracle Management Service Trace File

By default, the OMS will save all critical and warning messages to the emoms.trc file. However, you can adjust the amount of logging information that the OMS generates.

To change the amount of logging information generated by the OMS, run the following command:

emctl set property -name "log4j.rootCategory" -value "<LEVEL>, emlogAppender, emtrcAppender" -module logging

emctl set property -name <logging module> -value DEBUG -module logging

Controlling the Oracle WebLogic Server and Oracle HTTP Server Log Files

Oracle Management Service is a J2EE application deployed on an Oracle WebLogic Server. Different components of the Oracle WebLogic Server generate their own log files. These files contain important information that can be used later by support personnel to troubleshoot problems.

Table 11-6 lists the location of the log files for some components.

By default, the Enterprise Manager Grid Control configures OHS logs to rollover periodically to a new file, so that each file does not grow too large in size. You must also ensure that you delete the old rollover files periodically to free up the disk space. You can use an operating system scheduler, like cron on UNIX, to periodically delete the rollover files.

Refer to the Oracle Fusion Middleware Administrator's Guide for instructions on controlling the size and rotation of these log files.