DB2 FOR LUW / DB2FORLUW / A10 - DB2

In Version 10.1 Fix pack 4, the memory usage related to the 
execution of trusted routines increased significantly.  Up to an 
additional 9MB may be cached per agent/subagent when executing a 
combination of trusted routines (C, SQL).  Environments with 
persistent connections and configurations with subagent pooling 
(DPF and intra_parallelism) are more vulnerable as the memory 
usage is cached until the agent/subagent processes an 
application/connection termination.  If DB2's private memory 
usage increases significantly after upgrading to Version 10.1 
Fix Pack 4, and connections regularly execute trusted routines, 
this APAR is a likely cause. 
 
private memory usage can be monitored via the MON_GET_MEMORY_SET 
and MON_GET_MEMORY_POOL routines (values are in KB units), for 
example : 
 
db2 select MEMORY_POOL_TYPE, MEMORY_POOL_USED from 
table"(MON_GET_MEMORY_POOL('PRIVATE',null,null))" order by 
MEMORY_POOL_USED desc 
 
db2 select MEMORY_SET_TYPE, MEMORY_SET_USED from 
table"(MON_GET_MEMORY_SET('PRIVATE',null,null))"

**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 systems can be impacted                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5                       * 
****************************************************************

Problem first fixed in DB2 Version 10.1 Fix Pack 5

not known / see Local fix

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

30.07.2014
20.07.2015
16.02.2016