|
Problem IT01166
|
Status: Closed |
MEMORY ALLOCATED BY A MONITOR FUNCTION MIGHT NOT BE FREED UP AND MIGHT LEAK AFTER DATABASE IS DEACTIVATED |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Memory allocated by a monitor function might not be freed up
properly and might leak after database is deactivated.
It can be checked by the following command for monh pool (PoolID
11).
Memory allocated by File:2241390729 and LOC:905 is not freed for
a long time. (LOC 905 might be changed depending on the Fix
Pack.)
> db2pd -memblocks 11 sort
Memory blocks sorted by size for monh pool:
PoolID PoolName TotalSize(Bytes) TotalCount LOC File
11 monh 2153446 3801 905 2241390729
11 monh 239520 15 1889 3055296282
11 monh 139312 2 983 3400785722
11 monh 72000 2 266 3400632727
11 monh 6880 2 3898 3400632764
11 monh 960 2 350 882766201
11 monh 456 1 220 3402477436 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 FixPack 5 or higher *
**************************************************************** |
| Local Fix: |
Run "db2 flush package cache dynamic" before deactivating the
database.
It may not completely remove the memory leak, but it should
reduce memory that is leaking. |
| Solution |
Problem was first fixed in DB2 UDB Version 10.1 FixPack 5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.04.2014
29.07.2015
29.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
