Previous  Next          Contents  Index  Navigation  Glossary  Library

Duplicate Checking

By saving history for your alerts, you can define Oracle Alert to check for duplicates - that is, exceptions that existed in your database during a previous alert check. You can define Oracle Alert to perform alert actions when it finds these duplicate exceptions in your database. With duplicate checking, you can monitor outstanding items in your database until they are resolved. You can spend your time handling important business events, instead of following up on outstanding issues.

Checking for Duplicates

   To check for duplicates:

Note: You need to save history for your alert for at least one day longer than the frequency of the alert if you want to use duplicate checking. Oracle Alert cannot check for duplicates if history for the previous alert check is not retained. If you are defining a response set for your alert, save history for the number of response days in addition to the number of days you want to retain history.

   To check for duplicates at the action set level:

Note: Each action set duplicate configuration takes precedence over the alert duplicate configuration during an alert check.

   To flag duplicates in detail messages:

   To flag duplicates in summary messages:

See Also

Creating a Periodic Alert

Creating an Event Alert

Creating Alert Actions

Creating an Action Set for an Alert

Action Escalation


         Previous  Next          Contents  Index  Navigation  Glossary  Library