Scanning a database for exceptions

Visualizer lets you quickly identify exceptions to acceptable performance levels. Once a component exceeds the default or user-specified threshold level, you can scan the database and identify the problem object visually.

You need only scan a database if you are interested in exception history, summary, or detail reports. If you want an immediate display of exception values, select Options > Exceptions by Threshold. Subsequently drawn graphs display exceptions in a line-over-bar convention.

Scanning the database alters it by writing records for each value exceeded. Every time you update your database, scan it to get the most accurate exception summary, history, and detail reports.

There are two ways to scan a database for exceptions:

  • From Visualizer, select Database > Automator > Scan to run the event interactively.
  • As part of an Automator script, run an Automator Scan event (see Online Help for more information).

Automator displays the script log as it scans the database. The log also displays the time the event completes and any warnings and errors that occur during the scan event.

Note

Use the same dialog box to add or modify a Scan for Exceptions event. The dialog box title depends upon how you access it. 

Related topic

Using



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*