suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT19008 Status: Closed

CALLING DBMS_SQL ROUTINES CAN LEAK MEMORY BLOCKS.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 10.5                                          *
****************************************************************
Local Fix:
Avoid using leaking DBMS_SQL calls.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : 
follow-up : IT19150 IT19151 IT19152 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.01.2017
10.02.2017
10.02.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)