1 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Insert Information Protection Policy Classification from Slide 12

Setting up Incident Rules for

Database Metrics in
Enterprise Manager 12c.
Section 1:
About Incident Rules

Section 1: About Incident Rules

What are incident rules

What are incident rules applied to
When does an incident rule fire
Incident Management Ruleset for All Targets
The Impact of the default rule
Creating incident rules for database metrics

Section 2: Using a SQL Metric Extension to test incident rules

Section 3:Sending an SMS Text Alert

What are Incident Rules?

Incident Rules are a set of rules that describe how and under what
circumstances notification will occur.

Incident Rules specify the method of notification (email,snmp

trap,PL/SQL procedure, OS Command, SMS text )
Incident Rules specify the circumstances in which notification will occur
(for all database metric alerts, for a particular metric alert, for a
particular alert status)

What are Incident Rules applied to?

Database metrics
Job status changes
Self update alerts
Compliance rule violations
Metric evaluation errors
Service level agreement
Availability

This presentation focuses on setting simple incident rules for database metrics

When does the incident rule fire?

The agent evaluates that a metric threshold has been crossed

Or the agent receives this info from the database (in the case of server
generated alerts)
If the severity state has changed (eg. metric has changed to clear,
warning, critical from a previous state) the new severity state is uploaded
to the OMS
If the OMS has any incident rules which act upon this metric, they will be
applied.
The agent can be forced to resend the metric severity states by running
the command "emctl clearstate agent"

Incident management ruleset for all targets

Oracle provides an out of box rule called incident management ruleset
for all targets. This rule does the following:

Creates an incident for critical metric alerts

Clears metric alerts which are older than 7 days (and which are not
associated with incidents) - ie. means it will clear warnings
If the rule has been subscribed to it will also email the relevant EM
Administrator

Incident management ruleset for all targets

Demo

Summary
What is the impact of this rule (out of the box) ?

Critical alerts are shown on the database home page under "incidents and
problems region"
Warning alerts will not be shown on the database home page under
"incidents and problems region"
Warning alerts will be removed after 7 days
If the rule is subscribed to, email notification will only be sent for critical
metric alerts (not warnings)

If it is desired that warnings are shown on the home page, then create a new rule,
which creates an incident for warning alerts. See also Note:1494581.1 "Enterprise
Manager Cloud Control 12c is not showing Warning Alerts on the Database Home
Page"

Creating Incident Rules for Database Metrics

Flexible choices for creating new Incident Rules:

Choose that the rule will apply to all metrics or specify that the rule
will only act on only specific metrics.
Specify whether the metric will create an incident
Specify contacts to email
Specify any of the notification methods (which have been set up)
Possible for other EM administrators to subscribe to the rule
Possible to disable or enable the rule
Possible to re-order the rule

Setting up Incident Rules for

Database Metrics in
Enterprise Manager 12c.
Section 2:
Using a SQL Metric Extension
to test incident rules.

Demo Testing metric alerts using a Metric

Extension

Good for testing incident rules with because easy to simulate and
clear an alert condition
Metric Extension can run any customised SQL command

Demo Checking whether the notifications have

been sent?
How can we check whether Enterprise Manager sent the email/snmp trap
etc.

In incident manager, highlight the metric alert

On bottom half of screen click on events tab
Click on the message hyperlink
This shows the event details screen. View the last comment field
(email sent to)
Click on updates tab (this will show email and snmp trap details)

Remember the order of the incident rules are significant. They will be
applied in order

Setting up Incident Rules for

Database Metrics in
Enterprise Manager 12c.
Section 3:
Sending a SMS Text Alert

Demo How to set up SMS Notification in

Enterprise Manager 12c

Enterprise Manager 12c does not not directly support message services such as paging
or SMS, but instead relies on external gateways to perform the conversion from e-mail
to page/SMS
In this example, Enterprise Manager 12c sends the emails to an Orange email address
and Orange convert the emails to SMS text alerts

Orange email address

Specified as
<phonenumber@orange.net>

Orange Phone Number

Email to SMS conversion is on

Setting up an Incident rule to send an SMS text Alert

1) Create an email account with your mobile phone network provider. In this example it is
Orange/EE
http://email10.orange.co.uk/
2) The mobile phone network provider should have capability to convert emails to text. For
example, Orange has the option SMS alerts: ON
3) Test by sending a normal email to the orange email address. It can either user the orange email
address that was specified eg. rachelB@orange.net or it can take the syntax
<mobilephonenumber>@orange.net Confirm that this is converted to a SMS text message
4) In Enterprise Manager, go to:
<EM Username > (top right hand corner)
Click on enterprise manager password and email
Click on add another row
Click email type:pager short
Enter <your mobile phone number>@ORANGE.NET
Amend the incident rule and include Page <EM Administrator> (in the basic notifications section)

Create the Incident Rule - Demo

Click the powerpoint notes view for detailed instructions.