Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT05234 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
Lösung
This problem was first fixed in DB2 V10.1 FixPack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
29.10.2014
14.07.2015
14.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList