DB2 - Problembeschreibung
Problem IC68182 | Status: Geschlossen |
MEMORY LEAK IN APPLICATION HEAP WHEN CLIENT AND SERVER HAVE DIFFERENT CODE PAGE AND CONNECTION CONCENTRATOR IS ON | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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. | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in DB2 UDB Version 9.5 FixPack 6. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC68238 IC68239 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 26.04.2010 13.09.2010 20.12.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP6, 9.5.FP6.Or | |
Problem behoben lt. FixList in der Version |