DB2 - Problem description
Problem IC66149 | Status: Closed |
LARGE CPU OVERHEAD WHEN THE UOW EVENT MONITOR IS ACTIVE AND COLLECTING DATA | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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.7 Fix Pack 2 or higher. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
In V9.7 Fix Pack 2 the fast writer threads (db2fw0, db2fw1, db2fw2, db2fw3) will consume less CPU time. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC66555 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.02.2010 14.05.2010 14.05.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP2 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |