DB2 FOR LUW / DB2FORLUW / A50 - DB2

The condition to hit this issue, is to have the same DBMS_SQL 
call (like: open, fetch, ...) being called more than once. Once 
the problem happens, we can observe symptoms in output of the 
commands: 
 
DB2_PID=$(db2pd -edu | grep "db2sysc PID" | awk '{print $3}') 
 
db2pd -memblocks pid=$DB2_PID > memblock 
 
In case occurrence of this issue, in the output we will see many 
memory locations with following signature: 
 
Address            DataAddress        PoolID     PoolName 
BlkAge Size(Bytes)  I LOC   File 
0x0000000110390068 0x0000000110390080 0                       1 
504          1 150   2878669185 
 
Please note that line number (LOC) might change between 
fixpacks/releases, however we should still report extensive 
usage on the file 2878669185 itself.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to  DB2 Version 10.5 and Fix Pack 9                  * 
****************************************************************

Avoid using leaking DBMS_SQL calls.

Problem was first fixed in DB2 Version 10.5 and Fix Pack 9

not known / see Local fix

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

07.02.2017
27.09.2017
27.09.2017

9.0.