|
Problem IC82646
|
Status: Closed |
MEMORY LEAK IN DATABASE HEAP USING REPLICATION |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
On DB2 version 9.8 only, running replication (or any other use
of the db2ReadLog API) will trigger a memory leak on the DB2
server each time the read log API is issued. The database heap
will grow inside of the database memory area, which can
eventually lead to performance degradation from paging or STMM
detuning, and other errors/symptoms related to memory
exhaustion.
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 slightly across different
DB2 releases/Fix Packs):
PoolID PoolName Size(Bytes) LOC File
2 dbh 2728 1476 2986298236 |
| 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 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.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
|
 |
