home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC66555 Status: Closed

LARGE CPU OVERHEAD WHEN THE UOW EVENT MONITOR IS ACTIVE AND COLLECTING
DATA

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
When an UOW, Activities, Locking or Package Cache event monitor 
is active and collecting data, workloads can experience a large 
CPU overhead by the fast writer threads which are processing and 
committing the event monitor records.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Anybody using an UOW, Activities, Locking or Package Cache   * 
* event monitor.                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When an UOW, Activities (SQL Table only, not File or Pipe),  * 
* Locking or Package Cache event monitor is active and         * 
* collecting data, the fast writer threads can consume a large * 
* amount of CPU time.                                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.8 Fix Pack 3 or higher.                        * 
****************************************************************
Local Fix:
Solution
In V9.8 Fix Pack 3 the fast writer threads (db2fw0, db2fw1, 
db2fw2, db2fw3) will consume less CPU time.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.02.2010
20.12.2010
20.12.2010
Problem solved at the following versions (IBM BugInfos)
9.8.FP3
Problem solved according to the fixlist(s) of the following version(s)