The agent on your OMS server may report the following alert:
Target type=OMS and Repository
Target name=Management Services and Repository
Message=Average event dequeue time is %value% milliseconds, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. Dequeue time may get worse if queue table (EM_EVENT_BUS_TABLE) needs maintenance.
Event reported time=Jan 16, 2013 1:13:31 PM PST
Event Type=Metric Alert
Metric Group=Event Status
Metric=Average Event Dequeue Time (Milliseconds)
Rule Name=TEST,Incident creation Rule for metric alerts.
Update Details: Average event dequeue time is %value% milliseconds, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. Dequeue time may get worse if queue table (EM_EVENT_BUS_TABLE) needs maintenance
In your log files you’ll find a reference to error BEA-37. This error, which first appeared in 11g Grid Control, can safely be ignored. However, it does show up as a Warning in your OMS console and the email notice makes it appear quite serious.
The BEA-37 is a genuine error on your Weblogic administrative server, but I’ve been assured by Oracle Support that it has no impact on Enterprise Manager.
You can edit the configuration of the EM agents on your OMS server to disable reporting on this error.
Shut off the emagent on your OMS server
Make a backup copy of . ..agent_inst/sysman/config/emd.properties
Add the two lines below to emd.properites (
Restart the agent
# EM agent should ignore BEA-337 warnings from Weblogic
If the problems continue, you can adjust the metric threshold through the console.
From the Setup drop-down, select Manage Cloud Control | Health Overview
From the OMS and Repository drop-down over on the left side, now select All Metrics
Expand the Event Status group
Select Average Event Deque Time metric and you’ll see the history of these warnings and alerts
Press the Modify Thresholds button to adjust the values. See illustration below