DB2 FOR LUW / DB2FORLUW / A10 - DB2

Memory Usage in the Application Heap will grow during the scope 
of a connection when the db2ReadLog API is called.  This problem 
only occurs for DB2 Version 9.8 and higher which uses multiple 
agents to enhance the performance of log scanning.  Replication 
applications may be impacted.  A workaround is to periodically 
recycle the application / connection, which frees the entire 
application heap for the connection. 
 
In order to diagnose this problem: 
Monitor for constantly increasing memory usage of Application 
Memory in any of : 
 
db2pd -dbptnmem 
(See the "Used" value for the APPL-<database> consumer) 
 
db2pd -db <db> -memsets 
(see the "Used" column for the "AppCtl Memory Set) 
 
where available, use the MON_GET_MEMORY_SET routine 
(see the MEMORY_SET_USED for the APPLICATION memory set) 
 
 
Monitor for constantly increasing Application Heap usage, 
especially an application known to be calling the db2ReadLog api 
 
db2pd -db <db> -mempools 
(see the PhySz column for any memory pool where PoolName = apph) 
 
examine an application snapshot for an application with high 
application memory usage 
 
where available, use the MON_GET_MEMORY_POOL routine 
(see the MEMORY_POOL_USED value for any memory pool of type 
"APPLICATION") 
 
Using "db2pd -db <db> -memblocks all", confirm that memory 
blocks are accumulating where the "File" value matches the 
following: 
 
Memory blocks sorted by size for apph pool: 
PoolName TotalSize(Bytes) TotalCount LOC  File 
apph        286880616         442717     148   605356440

**************************************************************** 
* USERS AFFECTED:                                              * 
* Systems where replication is performed (or other use of the  * 
* db2ReadLog api)                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************

Periodically recycle any application (such as replication) with 
a persistent connection which makes use of the db2ReadLog API 
call.

First fixed in DB2 Version 10.1 Fix Pack 1

See Local Fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

27.04.2012
02.11.2012
02.11.2012