|
Problem IC73658
|
Status: Closed |
MEMORY LEAK IN APPLICATION HEAP DURING REBIND |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
Memory leak in application heap happens during rebind
The leak can occur on any rebind that specifies an option such
as RESOLVE, REOPT or VERSION
Note that a rebind can come from the REBIND command, db2rbind
(which by
default specifies RESOLVE CONSERVATIVE) or by calling the
SYSPROC.rebind_routine_package() routine |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users running rebind repeatedly from a session *
****************************************************************
* PROBLEM DESCRIPTION: *
* Users who run rebind of any form repeatedly from a single *
* session will experience this defect. *
* The symptom of this defect is observed with an abnormally *
* high and growing size of application heap *
****************************************************************
* RECOMMENDATION: *
* Users can upgrade to DB2 V9.5 fix pak 8 to avoid this *
* defect. *
* Or, they can avoid running repeated rebind of any form from *
* same session. *
**************************************************************** |
| Local Fix: |
Avoid using repeated rebind from a session. Or, don't use
RESOLVE, REOPT or VERSION option with the rebind syntax |
| available fix packs: |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
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 Version V9.5 fix pak 8
With the fix of this defect in place users will not experience
any abnormally high size of application heap over the time when
running any form of rebind from a single session. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.01.2011
05.07.2011
05.07.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
