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

MINOR MEMORY LEAK WHEN USING FEDERATION PASSTHRU FEATURE.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When user runs some query in passthru session like this 
set passthru server1; 
select * from sometable; 
set passthru reset; 
 
and then dump the DB2 memory blocks using db2pd like "db2pd 
-memblock", they can see some leaked memory blocks like below: 
 
Address            PoolID   PoolName   BlockAge   Size(Bytes) I 
LOC   File 
0x0000000110E7EB88 88         private      445   16           1 
451   2074526459 
0x0000000110E7EBC8 88         private      452   16           1 
451   2074526459 
0x0000000110E7ECA8 88         private      450   144          1 
451   2074526459 
0x0000000110E7ED68 88         private      451   144          1 
451   2074526459 
0x0000000110E7EEA8 88         private      457   144          1 
451   2074526459 
0x0000000110E7EF68 88         private      458   144          1 
451   2074526459 
0x0000000110E7F0A8 88         private      461   144          1 
451   2074526459 
0x0000000110E7F168 88         private      462   144          1 
451   2074526459 
 
In databases with health monitor enabled and Federated 
datasource servers defined, this issue manifests itself even 
though user doesn't run explicitly and passthru commands.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Server configured in Federation.                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When user runs some query in passthru session like this      * 
*                                                              * 
* set passthru server1;                                        * 
*                                                              * 
* select * from sometable;                                     * 
*                                                              * 
* set passthru reset;                                          * 
*                                                              * 
*                                                              * 
*                                                              * 
* and then dump the DB2 memory blocks using db2pd like "db2pd  * 
*                                                              * 
* -memblock", they can see some leaked memory blocks like      * 
* below:                                                       * 
*                                                              * 
*                                                              * 
* Address            PoolID   PoolName   BlockAge              * 
* Size(Bytes) I                                                * 
* LOC   File                                                   * 
*                                                              * 
* 0x0000000110E7EB88 88         private      445   16          * 
* 1                                                            * 
* 451   2074526459                                             * 
*                                                              * 
* 0x0000000110E7EBC8 88         private      452   16          * 
* 1                                                            * 
* 451   2074526459                                             * 
*                                                              * 
* 0x0000000110E7ECA8 88         private      450   144         * 
* 1                                                            * 
* 451   2074526459                                             * 
*                                                              * 
* 0x0000000110E7ED68 88         private      451   144         * 
* 1                                                            * 
* 451   2074526459                                             * 
*                                                              * 
* 0x0000000110E7EEA8 88         private      457   144         * 
* 1                                                            * 
* 451   2074526459                                             * 
*                                                              * 
* 0x0000000110E7EF68 88         private      458   144         * 
* 1                                                            * 
* 451   2074526459                                             * 
*                                                              * 
* 0x0000000110E7F0A8 88         private      461   144         * 
* 1                                                            * 
* 451   2074526459                                             * 
*                                                              * 
* 0x0000000110E7F168 88         private      462   144         * 
* 1                                                            * 
* 451   2074526459                                             * 
*                                                              * 
*                                                              * 
*                                                              * 
* In databases with health monitor enabled and Federated       * 
*                                                              * 
* datasource servers defined, this issue manifests itself even * 
*                                                              * 
* though user doesn't run explicitly and passthru commands.    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Recommended to move to V9.7 Fix pack 2.                      * 
****************************************************************
Local-Fix:
Not available.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
The issue was fixed in V9.7 Fix Pack 2.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.02.2010
17.05.2010
01.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList