DB2 Version 9.7 for Linux, UNIX, and Windows

ACTIVITYTOTALTIME threshold

The ACTIVITYTOTALTIME threshold specifies the maximum amount of time that the data server should spend processing an activity.

Type: Activity
Definition domain: Database, service superclass, service subclass, work action, workload
Enforcement scope: Database
Tracked work: Recognized coordinator and nested activities (see Activities)
Queuing: No
Unit: Time duration expressed in seconds (starting with DB2 Version 9.7 Fix Pack 5), minutes, hours, or days. If the time unit specified is seconds, this value must be a multiple of 10.
Predictive or reactive: Reactive

This time represents the entire lifetime of the activity, which includes any time spent waiting on workload management queues, and any other wait times that are incurred while the activity is executing, such as lock wait times. When a cursor is opened, the activity associated with the cursor lasts until the cursor is closed.

When a time threshold is applied to a stored procedure, it also applies to work happening inside the stored procedure. Consequently, when a stored procedure time threshold expires, any work happening inside the stored procedure is stopped. Hierarchies of stored procedure invocations can lead to hierarchies of time thresholds being applied to activities executing in the innermost levels of nesting. The most restrictive time threshold in the hierarchy (that is, the time threshold with the closest deadline) is always the one that applies.

The data server considers IMPORT, EXPORT, and other CLP commands to be user logic. Activities that are invoked from within IMPORT, EXPORT, and other CLP commands are subject to thresholds.