|
Problem IC64193
|
Status: Closed |
THE CHECKING INTERVAL FOR THE CPUTIME AND ROWSREAD WLM THRESHOLDS DOES NOT WORK PROPERLY ON 32-BIT PLATFORMS |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The checkinterval for the rowsread and cputime thresholds does
not work properly on 32-bit platforms. The value specified is
effectively ignored, and these thresholds are checked every
second (or more frequently). This can lead to severe
performance problems. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users who use the CPUTIME, CPUTIMEINSC, ROWSREAD or *
* ROWSREADINSC WLM thresholds on 32-bit platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* For the CPUTIME, CPUTIMEINSC, ROWSREAD and ROWSREADINSC WLM *
* thresholds, the check interval controls how often these *
* thresholds are evaluated while a query is running. The check *
* interval is user configurable when the thresholds are *
* created, the default is 60 seconds. A low check interval has *
* the trade off that the thresholds will detect violations *
* more quickly, at the expense of evaluating more frequently *
* (which will consume resources). *
* On 32-bit platforms, the check interval is ignored and *
* checking occurs at a 1 second (or lower) interval. This may *
* result in performance problems if the threshold is applied *
* to a large number of statements executing concurrently. *
* There is no work around. *
* A user encountering this problem would see higher than *
* expected CPU consumption on statements on which the *
* thresholds were applied. Problem would only be encountered *
* on 32-bit platforms, and only for the 4 thresholds listed. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW Version 9.7 Fix Pack 1 *
**************************************************************** |
| Local Fix: |
No local fix other than avoiding use of the cputime and
rowsreadthresholds on 32-bit platforms. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The problem is fixed in DB2 LUW Version 9.7, Fix Pack 1. There
is no workaround. The thresholds will still work, but will not
respect the checking interval and will consume more resources
than expected which may impact other work running on the system. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.10.2009
03.11.2009
03.11.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
