DB2 FOR LUW / DB2FORLUW / 980 - DB2

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

**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to v98fp5                                            * 
****************************************************************

fixed in v98fp5

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC83778 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

13.04.2012
13.08.2012
13.08.2012

9.8.FP5