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 IT05234 Status: Closed

UTL_FILE.FOPEN MIGHT CAUSE MEMORY LEAK IN THE KRCBH (DBMS SET).

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
db2pd -dbptnmem shows that DBMS set grows. The db2pd -memblocks 
indicates memory blocks for the system routines allocated in the 
krcbh heap keeps increasing as below; 
 
$ db2pd -memblock dbms 69 sort 
 
Memory blocks sorted by size for krcbh pool: 
PoolID PoolName TotalSize(Bytes) TotalCount LOC  File 
69     krcbh    190417520        4758633    2928 907928531 
 
Note: the LOC can slightly vary depending on the fixpack and/or 
platform. 
This symptom can be observed if application uses UTL_FILE.FOPEN, 
and the application keeps the database connection.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use UTL_FILE.FOPEN.                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 V10.1 FixPack 5 or later.              * 
****************************************************************
Local Fix:
Please disconnect the application which called UTL_FILE.FOPEN.
Solution
This problem was first fixed in DB2 V10.1 FixPack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.10.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