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

MEMORY ALLOCATED BY A MONITOR FUNCTION ON STANDBY MIGHT NOT BE FREED UP
AND MIGHT LEAK AFTER DATABASE IS DEACTIVATED/TAKEOVER

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
The fix for APAR IT19483 is incomplete, as a result, even with
its fix, the memory allocated by the monitor function on a HADR
standby database might not be freed up properly and might leak
after the database is deactivated/takeover.

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 subpool: (PoolID: 11,
SecondID: 0, PoolAddr: 0x078000000002F328)
PoolID     PoolName   TotalSize(Bytes)     TotalCount LOC   File

11         monh       27488322             138356     1162
2241390729
Total size for monh subpool: 27488322 bytes (PoolID: 11,
SecondID: 0, PoolAddr: 0x078000000002F328)
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
****************************************************************
Local Fix:
Have to restart the instance to free up the leaked memory.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.11.2018
16.01.2020
16.01.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)