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 IC78475 Status: Closed

MEMORY LEAK IN BPS COMPONENT DURING DATABASE DROP

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
Memory leak happen in BPS component during database drop. Each 
database drop will cause 8192 bytes memory leak in OSSe private 
memory pool. 
 
db2pd -memb could be used repeatedly following each database 
creation and drop to show the memory leak: 
 
> OSSe       OSSe       81920                10         4387 
sqlbptbl.C  <----------------- 
< OSSe       OSSe       8192                 1          4387 
sqlbptbl.C 
 
This shows we leak 8192 bytes for each database creation.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* MEMORY LEAK IN BPS COMPONENT DURING DATABASE DROP            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.5 fix pack 9                    * 
****************************************************************
Local Fix:
There is no workaround.
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 UDB Version 9.5 fix pack 9
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC78675 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.09.2011
04.04.2012
04.04.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList