home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC90228 Status: Geschlossen

USING XML IN QUERIES WITH REOPT BIND OPTION OR EXTENDED INDICATORS LEAKS
MEMORY IN DATABASE HEAP IN DPF ENVIRONMENTS

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
A problem was introduced in DPF (multiple data partition) 
configurations in DB2 Version 9.7 Fix Pack 7 and Version 10.1 
Fix Pack 2 where memory is leaked on every recompile of a query 
referencing XML data.  Approximately 40K is leaked on each 
occurrence - the memory is allocated from the Database Heap 
memory pool inside the Database Memory set. 
 
Monitoring tools such as MON_GET_MEMORY_POOL, database snapshot, 
db2pd -alldbs -mempools will show the database heap continually 
growing in size. 
 
db2pd -alldbs -memblocks db 2 
will show a growing number of blocks similar to : 
Address            DataAddress        PoolID     PoolName 
BlkAge Size(Bytes)  I LOC   File 
0x07000004B1C3ED68 0x07000004B1C3ED80 2          dbh 
58235 2504         0 2228  1235116617 
0x07000004B1B30A48 0x07000004B1B30A60 2          dbh 
58233 2504         0 2228  1235116617 
0x07000004B1B31428 0x07000004B1B31440 2          dbh 
58229 2504         0 2228  1235116617 
... 
 
Note the Size, LOC values may differ slightly, but the File 
value will be consistent.  It is also normal to have a buildup 
of allocations similar to this after database activation as 
tables are first accessed.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Systems using XML data in DPF environements together with    * 
* reopt bind option OR extended indicators                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix pack 8                        * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem first fixed in DB2 Version 9.7 Fix Pack 8
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC90241 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.02.2013
10.07.2013
10.07.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP8
Problem behoben lt. FixList in der Version
9.7.0.8 FixList