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 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. 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. 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 logs any problems it finds to this file. 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:.
The Management Agent log files are stored in the following directory when you install the Management Agent:. 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. 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.
Locate the emd. Use the information in Table to locate and modify the Agent logging and tracing properties in the emd. To modify the amount of information save d in the Management Agent trace file:. Open the emd. 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 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:. Open the emagentlogging. 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.
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.
Skip Headers. Contains all informational messages in local language. This will contain all actions the watchdog has performed. Contains all the trace messages in English only. This includes the PERL metrics and the discovery emdctl. 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.
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. Note: The values described in Table are case-sensitive. WARN Include warning information, in addition to critical errors. INFO Include informational messages, in addition to warning and critical error information. 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: Stop the Management Agent. Locate the emagentlogging. MaxFileSize When the fetchlet log file reaches this size, the Management Agent copies the logging data to a new rollover file and creates a new emagentfetchlet. MaxBackupIndex 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.
MaxFileSize When the fetchlet trace file reaches this size, the Management Agent copies the logging data to a new rollover file and creates a new emagentfetchlet. MaxBackupIndex This property indicates how many times the Management Agent will rollover the trace file to a new file name before deleting tracing data. 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.
To change the amount of tracing information generated by the Management Agent fetchlets: Stop the Management Agent. Note: The the values described in Table are case-sensitive. Enterprise Manager Control log file emctl. Oracle Management Service Message file emctl. Virtualization Management pack log file emovm.
Virtualization Management Pack trace file emovm. MaxBackupIndex This optional property indicates how many times OMS will rollover the log file to a new file name before deleting logging data. MaxBackupIndex This property indicates how many times the OMS will rollover the trace file to a new file name before deleting tracing data. To change the amount of logging information generated by the OMS, run the following command: emctl set property -name "log4j.
For example, oracle. Table lists the location of the log files for some components. All rights reserved. Book List. Contact Us. Log and trace information from the End-User monitoring Chronos scripts. Log file used by the Agent process. Log file for the Agent watchdog. Trace file used by the Agent process. The fetchlet log files used by the Management Agent for certain data-gathering tasks.
The fetchlet trace file used by the Management Agent for certain data-gathering tasks. Trace file for the PERL scripts. This includes the PERL metrics and the discovery. Log file for nfs agent during Oracle home patching. Include warning information, in addition to critical errors. It is not required to install a separate Perl kit. The Job model supported in previous releases is still available in this release in a similar, but not identical, fashion.
Jobs can be submitted, their status can be monitored, and their output checked. The Event model, as it existed in earlier versions, is no longer available. Instead, what is available is Targets.
Refer to Section D. In addition to running in the batch queue, EMAgent also submits a number of other tasks, typically related to actions required on other Oracle installations on the same host. The batch queue specified should run at the same priority level as all other general purpose processes on the system, typically 4.
For example,the following qualifiers would be typical for creating the batch queue that is used for EMAgent. EMAgent internally spawns a number of subprocesses and detached processes to run a majority of its tasks. The type of actions performed in these processes ranges widely from running simple DCL commands to running Java applications. It is imperative that the account used to install and run EMAgent not modify the typical OpenVMS session environment in any way that would alter the expected output of normal DCL commands.
COM file of the account used to start or stop the agent should not have any such redefinitions. If the redefinitions are required for any reason, then it is recommended that they be disabled in the batch mode, because EMAgent runs in the batch mode. These are the Targets files and the Properties files. However, these cannot be used directly. It is then possible to manage the targets from the EM Console.
This property indicates the time zone in which EMAgent is running. To update this property in the EMD. EMAgent is submitted as a batch job into the agent batch queue whenever it is started. Refer to the latest version of this log file. If it is readable not locked by a running EMAgent process , look through the file to see if there are any failure messages. Typical errors would be Failure to launch the EMAgent because of some issues with related shared libraries.
LOG , look at the emagent.
0コメント