Capturing More Information From Your Enterprise Manager Logs

by bluemedora_editor on December 16, 2013

Through the course of troubleshooting various Oracle Enterprise Manager Extensions, I have found one log file particularly helpful. This is the emoms.trc file. Breaking down the acronym we can see that this is the Enterprise Manager Oracle Management Server trace log file. This is referred to by Oracle as the general Enterprise Manager log. The emoms.trc log file can be used to troubleshoot Enterprise Manager startup issues, or even third party connectors.

As helpful as this log file is, we are still missing some of the log entries. In order to get all of the possible entries to troubleshoot the toughest of problems, we must set the log capture to a maximum level of DEBUG. In previous versions of Enterprise Manager, we were able to simply edit a line in theemoms.properties file and restart the OMS. For anyone using release 3 or newer of Enterprise Manager 12c, this is now handled by the emctl set property command.

The following is the base command to change the amount of logging information generated by the Oracle Management Server:

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

Notice that this command requires a <LEVEL> to be set. This value can be DEBUG, INFO, WARN, or ERROR. The emoms.trc among other OMS log files are grouped together and defined as root level log files. In my example below, I simply selected all of the root level log files by specifying the name in the parameter of “-name” set to “log4j.rootCategory”.

Example:

emctl set property -name "log4j.rootCategory" -value "DEBUG, emlogAppender, emtrcAppender" -module logging

[vc_single_image image=”1925″ alignment=”center” border_color=”grey” img_link_large=”” img_link_target=”_self” img_size=”full”]Turning on all of the log capabilities greatly increase the log file sizes and rate of collection for these files. It is my suggestion to turn the level down after troubleshooting is finished to avoid any potential system slow downs. To do this simply run the command again and substitute DEBUG for a lower level such as ERROR.

Thank you for taking time to learn how to set the emoms.trc log to a troubleshooting level. For more information on how to set specific log files or modules, refer to the section titled “Locating and Configuring Enterprise Manager Log Files” in the Enterprise Manager Administration Guide.

 

This blog was written by Brian Williams.  He is a Support Engineer with Blue Medora with over 7 years of IT, Testing, and Software Support experience, with a focus on Enterprise Manager Extensibility.

Get started

Try BindPlane for free. No credit card required.

Sign up
True Visibility
BindPlane for VMware vRealize Operations

True Visibility allows cloud management teams to use VMware vRealize’s powerful machine learning and capacity planning engine across their entire hybrid cloud environment.

Azure Monitor...everything
BindPlane for Microsoft Azure Monitor

Make Azure Monitor your first-pane-of-glass across your entire multi-cloud, multi-database or hybrid platform environment.

Thank you for contacting us. Your information was received. We'll be in touch shortly.