DB2 FOR LUW / DB2FORLUW / A10 - DB2

Large monitor routine allocations (eg. from 
MON_GET_PKG_CACHE_STMT) should not be allocated from application 
heap as the Application shared memory area was not designed for 
the single large temporary requirements.  They will be moved to 
private memory which is more dynamic in terms of virtual 
allocations (private memory can be "unmapped") and no longer 
under control of Application Heap size (APPLHEAPSZ).

**************************************************************** 
* USERS AFFECTED:                                              * 
* All systems, especially systems running OPM                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4                       * 
****************************************************************

Change APPLHEAPSZ to the default AUTOMATIC, or increase the 
fixed limit, or increase Instance Memory limit.  When using the 
MON_GET_PKG_CACHE_STMT routine it is advised to use filtering to 
reduce memory allocation requirements.

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

Problem first fixed in DB2 Version 10.1 Fix Pack 4

see Local Fix

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

15.11.2013
16.06.2014
16.06.2014