Vous êtes sur la page 1sur 15

Defining Escalating Actions:

NOTE: 1) Before you define an escalating action, make sure you first define an alert, and save history 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 Alert to 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;

WHERE ROWID = :ROWID; Step 2 : Click Alert Details Button Check the Check for Duplicates check box for an output if you want Oracle Alert to consider that output's exception value when it checks for duplicates. The default value is checked.

Step 3 : Click Action Button In the Actions window, create the actions you want Oracle Alert to perform if it finds duplicate 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.

Click Action Details Button

Step 4: Creating Escalation Group Navigation: Tools -- > Escalation Group

Note: The list contains only actions created for this alert that are of the same type as the escalation group type. Level Field Oracle Alert assigns an escalation level to each action in the escalation group and automatically defaults to the next available number for each successive action. You can change the escalation level of an action. Each time Oracle Alert checks the alert and finds the same exception, it performs the next higher level of action in the escalation group. Once it reaches the highest enabled action level Oracle Alert continues to perform that action until the exception is removed from your database.

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 an escalation 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 Alerts form, Oracle Alert performs each action in the escalation group. Once it has performed the highest level action, Oracle Alert no longer performs any action within that escalation group, even if the exception remains in your database. For example, suppose you define actions of levels 1 and 2. When Oracle Alert first detects 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 not perform the level 2 action again. 3) If you uncheck the Suppress Duplicates check box, Oracle Alert performs each action at the appropriate level, but when it reaches the highest level action it continues to perform 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 Suppress Duplicates check box, Oracle Alert includes any duplicate exception in the summary message, but flags each duplicate found with an asterisk (*).

Step 6: Update 1:

Update 2:

Update 3:

Update 4 :