ScanInterval

The ScanInterval parameter determines how frequently the High-speed Apply Engine scans its own internal processes to determine if any of the triggers defined by other [MonitorTuning] parameters have been activated. 

Attributes

This parameter has the following attributes:

Attribute

Value

Section

[MonitorTuning]

Abbreviation

None

Required?

No

Valid values

An integer from 1 to 32767

Default value

1

Related topic

MonitorTuning-parameters

Usage

Use this parameter to determine the precision with which High-speed Apply Engine monitors the triggers set by other [MonitorTuning] parameters. Normally, the scan interval should be short enough to ensure that High-speed Apply Engine will not activate one of the progress messages triggered more than once during the scan interval.

For example, assume that for diagnostic reasons, you set the CommitTrigger and CommitValue parameters to display progress messages after every 10 committed SQL statements. If you set the ScanInterval parameter to 30 seconds, the High-speed Apply Engine might commit 100 statements before High-speed Apply Engine checks to determine if your trigger has been activated. Your progress messages would not have the scope you desire.

Tip

We recommend that you do not change the default value of this option unless you have a specific reason to do so. You can consult BMC Support before changing this option.


 

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