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 IT01986 Status: Geschlossen

MEMORY LEAK HAPPENS WHEN FEDERATED SET TO 'Y'

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
If the db2 dbm config has the FEDERATED parameter set to 'Y', 
then there is memory leak for any query with or without 
federated server nicknames. 
The problem exists in DB2 v10.1  and any after that. 
 
The memory leak could  be  reproduced by using following steps 
where the FEDERATED dbm config  parameter is set to YES and a 
query is issued with a non-existent table. 
 
$ db2 get dbm cfg | grep FEDERATED 
 Federated Database System Support           (FEDERATED) = YES 
 
$ db2 select * from blah 
SQL0204N  "XXX.BLAH" is an undefined name.  SQLSTATE=42704 
 
$ db2pd -memblocks pid=`db2pd -edus|awk '/db2sysc PID/ {print 
$NF}'` sort|egrep "sqlqg_misc.C|sqlqg_catalog.C" 
0                     984                  9          451 
sqlqg_misc.C 
0                     249                  21         1874 
sqlqg_catalog.C 
 
$ db2 select \* from blah 
SQL0204N  "XXX.BLAH" is an undefined name.  SQLSTATE=42704 
 
$ db2pd -memblocks pid=`db2pd -edus|awk '/db2sysc PID/ {print 
$NF}'` sort|egrep "sqlqg_misc.C|sqlqg_catalog.C" 
0                     1312                 12         451 
sqlqg_misc.C 
0                     308                  28         1874 
sqlqg_catalog.C
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using FEDERATED=YES                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Users can upgrade to DB2 Version 10.1 fix pack 5 or higher   * 
* to avoid this defect                                         * 
****************************************************************
Local-Fix:
Set the dbm config  parameter FEDERATED=NO
Lösung
First fixed in DB2 Version 10.1 fix pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
23.05.2014
12.08.2015
12.08.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList