|
Problem IC82662
|
Status: Closed |
MEMORY LEAK USING TWO_PHASE COMMIT TRANSACTIONS AND ACTIVITY INVOLVING LOG SCANNING |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - 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 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* upgrade to v98fp5 *
**************************************************************** |
| Local Fix: |
|
| Solution |
fixed in v98fp5 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC83778
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.04.2012
13.08.2012
13.08.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.5
|
 |
