DB2 - Problem description
Problem IC63996 | Status: Closed |
SET CURRENT LOCALE STATEMENTS ARE NOT REMOVED FROM THE DYNAMIC SQL CACHE RESULTING IN A SYSTEM SLOWDOWN. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
SET CURRENT LOCALE statements are introduced into the cache by frequent connections. This can cause high CPU usage and performance degradation. The reason for the performance degradation and high CPU usage is because the SET CURRENT LOCALE statements are not removed from the dynamic SQL cache. In such a situation, the application snapshot may show many applications in a 'Compiling' state and CPU usage may increase. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All - High volume of concurrent connections is particularly * * susceptable * **************************************************************** * PROBLEM DESCRIPTION: * * CPU increase * **************************************************************** * RECOMMENDATION: * * upgrade to db2 V9.7 fp1 * **************************************************************** | |
Local Fix: | |
Set up connection pooling at the client to lower the frequency of new connections at the server | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Fixed in db2 V9.7 fp1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.10.2009 18.01.2010 18.01.2010 |
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 |