DB2 - Problem description
Problem IC73915 | Status: Closed |
THROUGHPUT DECREASE AND CPU USAGE INCREASE WHEN STATEMENT MONITOR SWITCH ON | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When a significant number of applications are executing a small number of statements, turning on statement monitoring may result in CPU spiking and reduced throughput as latch contention occurs in the dynamic SQL entries in the package cache. Stack dumps will show the sqlra_anchor_stmt as being the contentious latch. Various calling stacks are possible and are not included here. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * statement monitor enabled * **************************************************************** * PROBLEM DESCRIPTION: * * performance degradation with statement monitor enabled * **************************************************************** * RECOMMENDATION: * * move to DB2 for LUW version 9.7, fixpack 4 * **************************************************************** | |
Local Fix: | |
turn off statement montoring. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
fixed in DB2 for LUW version 9.7, fixpack 4 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC74395 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.01.2011 13.05.2011 13.05.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |