DB2 FOR LUW / DB2FORLUW / A10 - DB2

MON_GET_MEMORY_SET is not displaying the correct memory set 
statistic for "MEMORY_SET_SIZE".  It is intended to represent a 
point-in-time maximum memory commitment limit (as controlled by 
the instance_memory governance).  Instead it represents an 
internal virtual memory accounting amount, and in many cases 
will significantly overstate the "maximum memory commitment 
limit" (also known as instance memory usage/reservation) 
 
As an example, after increasing and decreasing the database 
memory configuration for the SAMPLE database, we have correct 
values shown through the db2pd -dbptnmem and -memsets tools, but 
MON_GET_MEMORY_SET overstates the memory set size/limit. 
 
db2pd -dbptnmem: 
Name             Mem Used (KB) HWM Used (KB) Cached (KB) 
======================================================== 
... 
DB-SAMPLE               145152       1137152       24064 
 
The 145152 KB amount is the correct size / instance memory used 
statistic. 
 
db2pd -db sample -memsets : 
Memory Sets: 
Name         Address            Id          Size(Kb)   ... 
SAMPLE       0x0700000050000000 711983157   145216 ... 
 
Size is 145216 KB (a slight difference due to metadata). 
 
MON_GET_MEMORY_SET: 
db2 select MEMORY_SET_TYPE,MEMORY_SET_SIZE from 
table"(mon_get_memory_set('DATABASE',null,null))" 
 
MEMORY_SET_TYPE                  MEMORY_SET_SIZE 
-------------------------------- -------------------- 
DATABASE                                      1105068 
 
1105068 KB is the overstated amount.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the latest fix pack.                              * 
****************************************************************

The problem is fixed in DB2 UDB Version 10.1 Fix Pack 5

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

11.06.2014
13.07.2015
13.07.2015