Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC80394 Status: Closed

CHANCES OF MEMORY LEAK INTRODUCED IN VERSION 9.7 FIX PACK 5

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* N/A                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Install fix                                                  * 
****************************************************************
Local Fix:
n/a
available fix packs:
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 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

Solution
Install fix
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84259 IC84266 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.12.2011
06.06.2012
06.06.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.