My Oracle Support Banner

EM12c : How to Edit the Generic Operational Error Metric to Suppress a Critical Alert (Doc ID 2101547.1)

Last updated on AUGUST 19, 2022

Applies to:

Enterprise Manager Base Platform - Version and later
Information in this document applies to any platform.


It may be desirable to temporarily suppress alerts (like the one shown below) for the Generic Operational Error metric, once the underlying problem is understood.
Unfortunately, this option is not available in EM 12c Cloud Control.

Target type=Database Instance
Target name=<TARGET_NAME>
Message=Operational error (Process 0x0x35e...) detected in <PATH>/alert/log.xml at time/line number: Wed Jan 20 23:12:49 2016/198145.
Event reported time=Jan 20, 2016 11:15:36 PM EST
Target Lifecycle Status=Production
Operating System=Linux
Associated Incident Id=182010
Associated Incident Status=New
Associated Incident Owner=
Associated Incident Acknowledged By Owner=No
Associated Incident Priority=None
Associated Incident Escalation Level=0
Event Type=Metric Alert
Event name=adrAlertLogOperationalError:genericOperationalErrStack
Metric Group=Operational Error
Metric=Generic Operational Error
Metric value=Process 0x0x35e6aab80 appears to be hung in Auto SQL Tuning task
Key Value=Wed Jan 20 23:12:49 2016/198145
Key Column 1=Time/Line Number
Rule Name=SA-Database,DBA Metric Errors
Rule Owner=<USER>
Update Details:
Operational error (Process 0x0x35e...) detected in <PATH>/alert/log.xml at time/line number: Wed Jan 20 23:12:49 2016/198145.
Incident created by rule (Name = Incident management rule set for all targets, Create incident for critical metric alerts [System generated rule]).



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.