|
Problem IT19152
|
Status: Closed |
CALLING DBMS_SQL ROUTINES CAN LEAK MEMORY BLOCKS. |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - 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 11.1 Mod 2 Fix Pack 2 or higher *
**************************************************************** |
| Local Fix: |
Avoid using leaking DBMS_SQL calls. |
| available fix packs: |
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 11.1 Mod 2 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.02.2017
23.06.2017
23.06.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
