My Oracle Support Banner

EM 12c, EM 13c: ADR Incidents generated by the rdbms and detected by the EM 'Incident' metric do not generate Email Notification in Enterprise Manager onwards (Doc ID 2046362.1)

Last updated on SEPTEMBER 09, 2019

Applies to:

Enterprise Manager for Oracle Database - Version and later
Information in this document applies to any platform.


Certain 'Incidents' or 'problems' shown on the database home page, do not generate email notification beginning with Enterprise Manager (EM) Typically these incidents/problems will appear on the home page as:

Problem: <error code>


Problem: ORA 600
Problem: ORA 7445
Problem: ORA 700 [kgerev1]

and tend to be associated with an error, for example:

An access violation detected in /oracle/orabase/diag/rdbms/<sid>/<sid>/alert/log.xml at time/line number: Fri Aug 21 11:48:04 2015/213702.

These problems/incidents can also be seen in "Incident Manager":

  1. Go to the Database Home Page
  2. From the 'Oracle Database' drop down menu, select Monitoring then Incident Manager
  3. Click on the left hand link 'All open problems'

The 'incidents' or 'problems' that do not generate emails are all related to ADR incidents (which are originally raised by the rdbms).

To confirm whether these are ADR incidents, highlight the 'problem' line.

This shows that this is an ADR Incident.

These ADR incidents should be detected by the EM 'Incident' Metric which is normally enabled automatically out-of-the-box.  

If email notification is correctly received from the EM 'Incident' metric to report on an ADR incident, it will contain the event name of 'adrAlertLog%'



and the Metric Group=Incident

Example of a correctly received email notification from the 'Incident' metric





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.