Alert 2 - Defining Escalating Actions

8/13/2019 Alert 2 - Defining Escalating Actions

1/15

Defining Escalating Actions:

NOTE:

1) Before you define an escalating action, make sure you first define an alert, and savehistory for at least one day longer than the number of days between alert checks.

2) You also want to define at least two detail alert actions, one that you want Oracle Alert to perform during a first alert check, and a second that you want Oracle Alertto perform during a subsequent alert check if it finds the same exceptions.

Navigation:

Alert Manager -- > Alert - ->Define

Sample Code:

SELECT LAST_NAME, FIRST_NAME, EMPLOYEE_NUMBER INTO &LNAME,&FNAME,&ENUMBER FROM

PER_ALL_PEOPLE_F WHERE ROWID = :ROWID;


2/15

WHERE ROWID = :ROWID;

Step 2 :

Click Alert Details Button

Check the Check for Duplicates check box for an output if you want Oracle Alert toconsider that output's exception value when it checks for duplicates. The default value ischecked.

Step 3 :

Click Action Button

In the Actions window, create the actions you want Oracle Alert to perform if it findsduplicate exceptions across alert checks.

Note: You can use only detail level actions for action escalation, but you can define

as many detail actions as you like.


3/15

Click Action Details Button


4/15

Step 4:

Creating Escalation Group

Navigation: Tools -- > Escalation Group


5/15

Note: The list contains only actions created for this alert that are of the same typeas the escalation group type.

Level Field

Oracle Alert assigns an escalation level to each action in the escalation group and automaticallydefaults to the next available number for each successive action. You can change the escalationlevel of an action.

Each time Oracle Alert checks the alert and finds the same exception, it performs thenext higher level of action in the escalation group. Once it reaches the highestenabled action level Oracle Alert continues to perform that action until the exceptionis removed from your database.


6/15

Setp 5:

Perform escalated actions

Click Action Set Button from Alert window.

Invoke duplicate suppression

1) For each action set you define, you can choose to have Oracle Alert "suppress"duplicates. That is, you can have Oracle Alert stop performing the actions in anescalation group once it has performed the highest level action.

2) If you check the Suppress Duplicates check box in the Actions Sets window of the Alertsform, Oracle Alert performs each action in the escalation group. Once it has performedthe highest level action, Oracle Alert no longer performs any action within thatescalation group, even if the exception remains in your database.

For example, suppose you define actions of levels 1 and 2. When Oracle Alert firstdetects an exception, it performs the level 1 action. If, during the next alert check,Oracle Alert finds that same exception, Oracle Alert performs the level 2 action. If,during the third alert check, the duplicate exception still exists, Oracle Alert does notperform the level 2 action again.

3) If you uncheck the Suppress Duplicates check box, Oracle Alert performs each action atthe appropriate level, but when it reaches the highest level action it continues toperform that action as long as the exception remains in your database.

4) If your action set includes a summary message action and you check the SuppressDuplicates check box, Oracle Alert includes any duplicate exception in the summarymessage, but flags each duplicate found with an asterisk (*).


7/15

Step 6:

Update 1:


8/15


9/15

Update 2:


10/15


11/15


12/15

Update 3:


13/15


14/15


15/15

Documents

Alert 2 - Defining Escalating Actions