Perform the following diagnostic steps if messages are not being generated or updated as expected in Operations Manager.
Verify that the event that was triggered is referenced in a rule that forwards events to the OMU connector.
Determine the error that Oracle Enterprise Manager has reported by examining the log file for errors. Perform the following steps to locate errors in the log file:
Open the emoms.trc file in a text editor. The file is located in the log directory at the following location:
<EM_INSTANCE_BASE>/em/<OMS_NAME>/sysman/log/
... where <EM_INSTANCE_BASE> is the OMS Instance Base directory. By default, the OMS Instance Base directory is gc_inst, which is present under the parent directory of the Oracle Middleware Home.
For example, if the Oracle Middleware Home is /u01/app/Oracle/Middleware, then the instance base directory is /u01/app/Oracle/Middleware/gc_inst, and the log and trace files are available in the /u01/app/Oracle/Middleware/gc_inst/em/EMGC_OMS1/sysman/log/ directory path.
Go to the bottom of the file and search backwards for "Caused by."
Lines that start with "Caused by" contain error information. The error information appears after the text in the line that reads "oracle.sysman.emSDK.webservices.outbound.WSInvokeException: caught WebServiceException :".
Diagnose the problem based on the error information. See Resolving Errors from Oracle Enterprise Manager for information on troubleshooting common error events.