Last updated on JANUARY 22, 2016
Applies to:Enterprise Manager for Oracle Database - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
In a new incident management ruleset,the "Exclude Targets" parameter included a Group, which consists of several databases for which incidents or notifications should not be created or sent.
Even with the databases in the Group to be excluded, when the ruleset is evaluated, an incident is created and notification email sent.
The incident was generated from the ruleset in question as shown below:
Target type=Database System
Message=Target is down; 1 member is down: pizza
Event reported time=Jan 6, 2016 1:00:18 PM EST
Associated Incident Id=3045
Associated Incident Status=New
Associated Incident Owner=
Associated Incident Acknowledged By Owner=No
Associated Incident Priority=None
Associated Incident Escalation Level=0
Event Type=Target Availability
Root Cause Analysis Status=Symptom
Causal analysis result=Identified as a symptom with 1 causes
pizza Database Instance=Failed to connect to database instance: _V2_#sFailed to connect: java.sql.SQLException: Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor ;.
Rule Name=copy_of_ruleset_to_create_and_manager_incidents,Incident creation rule for a Target Down availability status
Target is down; 1 member is down: pizza
Incident created by rule (Name = copy_of_ruleset_to_create_and_manager_incidents, Incident creation rule for a Target Down availability status; Owner = SYSMAN).
It was expected that the excluded target databases in the group should not cause an incident to be created nor an email notification to be sent.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms