DB2 Version 9.7 for Linux, UNIX, and Windows

Time-based thresholds support finer granularity

The granularity for time-based thresholds has improved. This change helps reduce delays when early detection of excessive time consumption is important.

Table 1 summarizes the improvements in granularity of certain time-based thresholds in Version 9.7.

Table 1. Improved granularity of certain time-based thresholds
Threshold	Description	Granularity
CONNECTIONIDLETIME	Controls the maximum amount of time that a connection can be idle; that is, not working on a user request.	Changed from 5 minutes to 1 minute (as of Version 9.7)
ACTIVITYTOTALTIME	Controls the maximum lifetime of an activity.	Changed from 5 minutes to 1 minute (as of Version 9.7); and from 1 minute to 10 seconds (as of Version 9.7 Fix Pack 5)
UOWTOTALTIME	Controls the maximum amount of time that a unit of work can spend in the DB2® engine.	Changed from 1 minute to 10 seconds (as of Version 9.7 Fix Pack 6)