DB2 FOR LUW / DB2FORLUW / A10 - DB2

A small amount of memory used to track FMP (Fenced Mode Process) 
routine execution history may be leaked when FMP processes are 
failing to start or a threaded FMP process abnormally 
terminates.  The leak is typically a side-effect of some more 
severe problem which, if resolved, will avoid the leak. 
 
The memory is leaked in the APM or Agent pool management heap, 
which is allocated from the DBMS (Database Manager) memory set. 
The leak persists while the instance/member is active. 
 
Growth in the apm heap can be monitored via: 
db2pd -mempools (observe the statistics in the row with PoolName 
= apmh) 
On version 9.7 and higher, use the MON_GET_MEMORY_POOL routine 
and monitor the memory pool type of "APM" 
 
The specific memory allocations associated with the leak can be 
monitored with 
   db2pd -memblocks 70 
 
If the leak exists, there will be a large and growing number of 
allocations with a File value of 1411768028 and 1411768055 
All memory consumers in DBMS memory set: 
PoolID     PoolName   TotalSize(Bytes)     %Bytes TotalCount 
%Count LOC   File 
70         apmh       8416                 0.57   4 
0.63   815   1411768055 
70         apmh       352                  0.02   4 
0.63   164   1411768028

**************************************************************** 
* USERS AFFECTED:                                              * 
* All systems                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* This APAR documents a secondary symptom, it is recommended   * 
* to address the underlying problem                            * 
****************************************************************

Address the primary problem with FMP routine execution in order 
to avoid the memory leak

DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Problem first fixed in DB2 Version 10.1 Fix Pack 3

see Local Fix

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

05.12.2012
04.12.2013
04.12.2013