The following sections describe how to locate and configure the OMS log files:
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.
Oracle Management Service trace file (
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.
Oracle Management Service log file (
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.
Enterprise Manager Control message file
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.
The OMS Instance Base directory is
gc_inst in the Oracle Middleware Home (middleware home). This directory stores all log and trace files related to OMS 12c.
You can choose to change this, if you want, in the installer.
For example, if the Middleware home is
/u01/app/Oracle/Middleware/, then the instance base location is
/u01/app/Oracle/gc_inst. You can choose to change this, if you want, in the installer. However, you can change it for only advanced installation and not for simple installation.
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
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 Controlling the Size and Number of Oracle Management Service Log and Trace Files:
emctl set property -name <property> -value <property value> -module logging
The above command will set the property for all OMSes. If you want to set it for a single OMS, then specify an extra option
-oms_name as follows:
emctl set property -name <name> -value <value> -module logging -oms_name example.myco.com:portnumber_Management_Service
To set it for the current OMS, use the property -oms_name local_oms. To set it for any other OMS, you can provide the name of that OMS. The OMS name has to be similar to
In Oracle Enterprise Manager Cloud Control 12c, you do not have to restart OMS for the changes to take effect.
In Oracle Enterprise Manager Cloud Control 12c,
emctl set property by default sets the logging properties for all the OMS. To set the property for only one OMS, use the
Table 28-3 Oracle Management Service Log File Properties in the emomslogging.properties File
When OMS log file reaches this size, then OMS copies the logging data to a new rollover file and creates a new
This optional property indicates how many times OMS will rollover the log file to a new file name before deleting logging data. This property is also applicable for emoms_pbs.log.
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.
When the OMS trace file reaches this size, then OMS copies the logging data to a new rollover file and creates a new
This property indicates how many times the OMS will rollover the trace file to a new file name before deleting tracing data. This property is also applicable for emoms_pbs.trc.
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
The above command will change the log level for all OMS, unless
-oms_name option is specified.
If you change the
root logging level for the
emoms.trc file, then a lot of messages are written to the trace file filling up the space quickly, and potentially slowing down the system. Run the following command to enable debug selectively for specific modules that need to be assessed:
emctl set property -name <logging module> -value DEBUG -module logging
<logging module> represents the logging module from a specific subsystem.
The logging level can be changed for specific modules by running the following command:
emctl set property -name "<CATEGORY>" -value "<LEVEL>" -module logging
where LEVEL can be DEBUG, INFO, WARN, or ERROR, and CATEGORY is specific to the module for which level has to be changed. To change the logging module, contact Oracle Support.
The location of emoms.trc, emoms.log, emoms_pbs.trc, and emoms_pbs.log files can be changed to a different location from the default location. However, it is not advisable to do so.
Oracle Management Service is a Java EE 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 28-4 lists the location of the log files for some components.
Table 28-4 Component Log File Location
Oracle HTTP Server (OHS)
The log data from WebLogic will be at:
This log can be restricted, rotated by size, time, and other conditions from the WebLogic Console. The default settings are:
The messages written to sysout and syserr will be available in the .out files. They cannot be rotated by size or time. They are rotated only when the server starts. They are located at:
The node manager logs are at
By default, the Enterprise Manager Cloud Control configures Oracle HTTP Server logs to roll over 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.
Following are log files that you will need to maintain and manually purge:
All files under
<gc_inst>/user_projects/domains/<domain_name>/servers/ohs1/logs. For example:
em_upload_http_access_log.* access_log.* em_upload_https_access_log.* ohs1-*.log console~OHS~1.log* mod_wl_ohs.log*
For instructions on controlling the size and rotation of these log files, refer to chapter "Managing Log Files and Diagnostic Data" in Oracle Fusion Middleware Administrator's Guide.
For information about configuring Enterprise Manager to view Fusion Applications PL/SQL and C diagnostic log files, see chapter "Managing Oracle Fusion Applications Log Files and Diagnostic Tests" in the Oracle Fusion Applications Administrator's Guide.