Over the weekend our OMS crashed and I am trying to determine the cause and have two questions.
1) I believe the emoms.log & emoms.trc files are the appropriate files to examine, is this correct?
2) Is there documentation anywhere which helps explain how to read the emoms files? There is so much information I am having difficulty determining what is relevant and what is not.
3) Are there other logs I should be looking at?
Check out this chapter in the Admin guide Locating and Configuring Enterprise Manager Log Files
This log file contains trace, debug, information, error, or warning messages from the agent.
This log file contains logging information about fetchlets and receivelets.
This error log file contains information about errors. The errors in this file are duplicate of the errors in
This log tracks the metadata updates to the agent.
The information is saved to
emctl.log file, when you run the Enterprise Manager Control commands. For more information about
emctl.log file, see chapter Starting and Stopping Enterprise Manager Components.
OMS log and trace files store important information that Oracle Support can later use to troubleshoot problems. OMS uses the following six types of log files:
The Management Service saves information to the log file when it performs an action (such a starting or stopping) or when it generates an error. This is a log file for console application.
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. This is a trace file for Console application.
The Management Service saves information to this log file for background modules such as the loader, job system, event system, notification system, and so on. This file contains messages logged at ERROR or WARN levels.
This trace file provides additional logging for the background modules such as the loader, job system, event system, notification system, and so on when DEBUG or INFO level logging is enabled for these modules. This file can provide Support personnel with even more information about actions these modules were performing when a particular problem occurred.
The information is saved to
emctl.log file, when you run the Enterprise Manager Control commands. For more information about emctl.log file, see chapter Starting and Stopping Enterprise Manager Components.
This file is created by the HealthMonitor thread of the OMS when it restarts the OMS because of a critical error. This file is used for troubleshooting the OMS restart problem. It provides information such as the exact time when the OMS is restarted and which module has caused the crash.