Overview of Oracle Alert History
When you review Oracle Alert history, not only can you see a record of the exceptions that Oracle Alert found during an alert check, but you can also review the exact text of the action that Oracle Alert performed. Oracle Alert even preserves a record of the actions that you no longer use so that you can review the history of your exception reporting. And, you can review history for your response processing alerts, and see a complete record of responses received and response actions performed.
If you are saving history for an alert, you can define your alert to look for exceptions that existed during previous alert checks - known as duplicate exceptions. You can have Oracle Alert take certain actions based on the presence of these duplicate exceptions. And, you can create a series of escalating actions for Oracle Alert to perform when it finds the same exception over a period of time. Oracle Alert performs each action in sequence, then continues to perform the last action until the exception is removed from your database.
Basic Business Needs
In your business, you should be able to:
- Review exception reporting activity over any period of time.
- Review any exception found in your database during a particular period of time.
- Review the exact text of an alert message that Oracle Alert sent, even if you no longer use that message.
- Review any actions that Oracle Alert performed during an alert check, even if you no longer use those actions.
- Review responses received and response actions performed for your response processing alerts.
- Have Oracle Alert check for exceptions that remain in your database over a specific period of time.
- Have Oracle Alert perform certain actions if an exception exists in your database during consecutive alert checks.
- Define a series of actions, each action of an increasing severity level, and have Oracle Alert perform one action each time it encounters the same exception in your database.
Major Features
You can see a complete reconstruction of the actions taken by your alert during an alert check. You can see all the actions your alert performed, or you can enter search criteria to narrow the range of actions you want to review. When you review each action's history, you see the action exactly as it was performed by Oracle Alert, including the complete text of any message action, and the complete script of any SQL script or operating script action.
You can also review the exceptions found during an alert check. You can see all the exceptions found for your alert, or just those found for a particular action set. And, you can specify which particular exceptions you want to review. You do not have to sort through all of the exception information for a particular alert - you can simply choose to omit certain outputs, or restrict the length of other outputs, to make your history review more efficient.
Reconstruct complete history of the responses received and response actions performed for your response processing alerts.
Review by Range of Dates
Depending upon how much alert history you choose to preserve, you can review all exceptions found in your database over the period of time you specify. Or, you can look through all the history you are preserving and review all exceptions or actions for a particular alert.
You can define an alert to check for exceptions that remain in your database over time. Each time Oracle Alert encounters an exception it found during a previous alert check, it considers that exception a "duplicate" and can perform alert actions based on the presence of that duplicate exception. You determine which outputs Oracle Alert should consider when checking for duplicates, and you can turn duplicate checking "off" for any or all of your alert outputs.
You can create a set of actions - each action of a different level - that Oracle Alert performs if it finds the same exception during consecutive alert checks. Each time that Oracle Alert finds a duplicate exception, it performs the next level detail action. For every action level, you can define a different action. For each alert, you can define an unlimited number of escalation levels.
Once it has performed the highest level action, Oracle Alert can continue performing that action during each subsequent alert check; or with duplicate suppression, can cease performing actions altogether. Duplicate suppression lets you define Oracle Alert to perform each level of action in a group of escalating actions once only.
See Also
Duplicate Checking
Action Escalation
Reviewing Alert Actions
Reviewing Alert Exceptions
Reviewing Alert Checks
Creating Self-Referencing Alerts
