Database Reference
In-Depth Information
OMS Log and Trace Files
There are six main log and trace files used for troubleshooting issues with the OMS. These are located under the OMS
instance base directory ( gc_inst in Table 3-4 ). These files are as follows:
emctl.log contains output from emctl commands.
emctl.msg is generated when the OMS restarts because of critical errors.
emoms.log , the log file for the console, contains information created when the OMS performs
an action (such as starting or stopping) or generates an error.
emoms.trc contains more-detailed tracing information to support troubleshooting errors.
emoms_pbs.log contains errors or warnings for background modules such as the event and job
systems.
emoms_pbs.trc contains more-detailed tracing information to troubleshoot problems with
background modules.
As you might imagine, these files can quickly increase in size over time. Thankfully, the files have a predefined
maximum size before the OMS rolls information to a new file. The old versions of the file can be identified as EM
places a number in the name. For example, in my environment I can see the following files under the log directory:
[oracle@server log] ls -al
total 101600
drwxr----- 2 oracle oinstall 4096 Mar 30 22:38 .
drwxr----- 3 oracle oinstall 4096 Sep 19 2012 ..
-rw-r----- 1 oracle oinstall 5242789 Mar 18 01:08 emoms-156.log
-rw-r----- 1 oracle oinstall 5242789 Mar 18 01:08 emoms-156.trc
-rw-r----- 1 oracle oinstall 5241643 Mar 19 16:15 emoms-157.log
-rw-r----- 1 oracle oinstall 5241643 Mar 19 16:15 emoms-157.trc
-rw-r----- 1 oracle oinstall 5242832 Mar 21 08:27 emoms-158.log
-rw-r----- 1 oracle oinstall 5242832 Mar 21 08:27 emoms-158.trc
-rw-r----- 1 oracle oinstall 5241829 Mar 22 14:52 emoms-159.log
-rw-r----- 1 oracle oinstall 5241829 Mar 22 14:52 emoms-159.trc
-rw-r----- 1 oracle oinstall 5242518 Mar 24 13:55 emoms-160.log
-rw-r----- 1 oracle oinstall 5242518 Mar 24 13:55 emoms-160.trc
-rw-r----- 1 oracle oinstall 5236550 Mar 26 06:45 emoms-161.log
-rw-r----- 1 oracle oinstall 5236550 Mar 26 06:45 emoms-161.trc
-rw-r----- 1 oracle oinstall 5242710 Mar 28 01:34 emoms-162.log
-rw-r----- 1 oracle oinstall 5242710 Mar 28 01:34 emoms-162.trc
-rw-r----- 1 oracle oinstall 5242442 Mar 28 20:46 emoms-163.log
-rw-r----- 1 oracle oinstall 5242442 Mar 28 20:46 emoms-163.trc
-rw-r----- 1 oracle oinstall 5242752 Mar 30 22:38 emoms-164.log
-rw-r----- 1 oracle oinstall 5242752 Mar 30 22:38 emoms-164.trc
-rw-r----- 1 oracle oinstall 4709623 Apr 1 21:56 emoms.log
-rw-r----- 1 oracle oinstall 4709623 Apr 1 21:56 emoms.trc
You can control the number and size of these files by using an emctl command. The exact command varies
depending on which file you want to control. You can also control which information goes into emoms.trc . By default,
the OMS writes only warning and critical messages into the trace file, but you can change the level of information
written there by using the following command:
$ emctl set property -name "log4j.rootCategory" -value "<LEVEL>, emlogAppender, emtrcAppender"
-module logging
 
Search WWH ::




Custom Search