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

CHANCES OF MEMORY LEAK INTRODUCED IN VERSION 9.7 FIX PACK 5

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
In Version 9.7 Fix Pack 5, chances of having a memory leak have 
been introduced. To check if a memory leak has happened, issue 
the db2pd -memb command and check if the output of the command 
looks similar to the following output: 
 
Memory blocks sorted by size for private pool: 
PoolID     PoolName   TotalSize(Bytes)     TotalCount LOC   File 
88         private    264376936                      164622 
1541  2904145706 
88         private    131072                               1 
1287  789176096 
88         private    49152                                  5 
385   1234005865 
88         private    7072                                    2 
1253  2506170342 
88         private    4296                                    1 
246   2926445243 
 
Total size for PRIVATE memory set: 283633406 bytes 
 
Memory blocks sorted by size for private pool: 
PoolID     PoolName   TotalSize(Bytes)     TotalCount LOC   File 
88         private    283437968                     175389 
1541  2904145706 
88         private    131072                             1 
1287  789176096 
88         private    49152                                5 
385   1234005865 
88         private    7072                                2 
1253  2506170342 
 
The private memory usage in file 2904145706 at line 1541 keeps 
leaking and consumes physical memory. 
 
This memory leak can happen if a query uses a LOB locator for 
the output column. 
 
Example: 
ODBC  application does: 
select substr( clob_column, 1, 30 ) from t1 
SQLBindCol is done with with SQL_C_CLOB_LOCATOR 
 
The query is returning a LOB column, but the client wants a LOB 
locator.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* N/A                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Install fix                                                  * 
****************************************************************
Local-Fix:
n/a
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Install fix
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.06.2012
28.11.2012
28.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList