home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IT00589 Status: Closed

MEMORY LEAK IN PRIVATE POOL WHEN USING COMPLEX DATA TYPES

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
A memory leak may in private pool may occur if the application 
is using complex data types (CREATE TYPE ...), like ARRAY. 
 
The memory leak is in the DRDA layer of the DB2 engine and can 
be observed with db2pd -memblocks, it will show up as an 
allocation in pair's. 
For Example: 
 
... 
Memory blocks sorted by size: 
PoolID     PoolName   TotalSize(Bytes)     TotalCount LOC   File 
0                     91540064             14938      1127 
2904145706 
0                     69509904             11343      1620 
3103375146 
 
Please note that in the avobe example the LOC and File are 
specific to a DB2 release and may look different in other 
releases. Please check with DB2 Support if you suspect this 
memory leak.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 Version 10.1 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.03.2014
14.07.2015
14.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList