DB2 - Problem description
Problem IC83778 | Status: Closed |
MEMORY LEAK USING TWO_PHASE COMMIT TRANSACTIONS AND ACTIVITY INVOLVING LOG SCANNING | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
On DB2 version 9.8 and higher, a memory leak may occur whenever "non-recovery" log scanning activities read logs containing two-phase commit transactions. The leak occurs in the database heap and can accumulate quickly on systems where regular log scanning occurs, such as replication. Memory usage in the database heap can be monitored with the MON_GET_MEMORY_POOL routine (track the MEMORY_POOL_USED column) , or db2pd -db <db> -mempools (track the PhySz column), db2pd -db <db> -memblocks 2 will show an increasing number of records with the following LOC, File combination (LOC can differ across different DB2 releases, Fix Packs): PoolID PoolName Size(Bytes) LOC File 2 dbh 1480 905 242487389 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All systems * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 1 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 10.1 Fix Pack 1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.05.2012 31.10.2012 31.10.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.1 | |
10.5.0.1 |