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

MEMORY LEAK POSSIBLE ON WINDOWS IF A WINDOWS PERFORMANCE API FUNCTION
RETURNS AN UNEXPECTED RETURN CODE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Memory allocated in DB2 function  ossCollectRawCounterArrays, 
can be leaked if one of the Windows API functions in that 
function call did not return the expected return code. 
The Error handling routine then fails to free the right memory, 
leading to a memory growth. 
 
This memory leak may not be visible through db2pd -mempool or 
db2pd -dbptmem output.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 on Windows                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix    * 
* Pack 4) or Later                                             * 
****************************************************************
Local Fix:
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
First Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix 
Pack 4)
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.02.2014
13.10.2014
13.10.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList