DB2 - Problembeschreibung
Problem IC75027 | Status: Geschlossen |
MEMORY LEAK IN APPLICATION HEAP WHEN SUPPORT FOR EXTENDED INDICATORS FEATURE IS ENABLED | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
When support for extended indicators feature is enabled, you may find memory leak in application heap. Extended indicators support is a new feature from V9.7 Fix Pack 2 and is by default enabled in JDBC driver. You can monitor growing memory usage in application heap by running "db2pd -db DBNAME -memb appctl". The output(snippet) is shown below as an example. Memory blocks sorted by size for apph pool: PoolID PoolName TotalSize(Bytes) TotalCount LOC File 1 apph 11284444 245314 3982 1315556668 The application may eventually receive error SQL0954C. You may also find "Out of memory failure for Application Heap (APPLHEAPSZ)" error and SQLO_NOMEM_APPH in db2diag.log. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 5 * **************************************************************** | |
Local-Fix: | |
You can disable Extended Indicators support by specifying accordingly in the connection properties. The following is an example: String url = "jdbc:default:connection"; Properties prop = new Properties(); prop.put("enableExtendedIndicators", "2"); // public final static int NO = 2 try { con = DriverManager.getConnection(url, prop); | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 9.7 Fix Pack 5 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 14.03.2011 12.12.2011 12.12.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP5 | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |