DB2 - Problem description
Problem IC68182 | Status: Closed |
MEMORY LEAK IN APPLICATION HEAP WHEN CLIENT AND SERVER HAVE DIFFERENT CODE PAGE AND CONNECTION CONCENTRATOR IS ON | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
When your client application and database server have different code page and connection concentrator is on, the memory leak in application heap appears each time one statement is executed. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * When your client application and database server * * havedifferent code page and connection concentrator is on, * * thememory leak in application heap appears each time * * onestatement is executed. * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.5 FixPack 6.Or, set connection * * concentrator off or use the same codepage between server and * * client. * **************************************************************** | |
Local Fix: | |
Setting connection concentrator off or using the same code page between server and client. | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 9.5 FixPack 6. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC68238 IC68239 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.04.2010 13.09.2010 20.12.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP6, 9.5.FP6.Or | |
Problem solved according to the fixlist(s) of the following version(s) |