|
Problem IT00391
|
Status: Closed |
MON_GET_MEMORY_SET DISPLAYS WRONG MEMORY SET STATISTIC FOR MEMORY_SET_SIZE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All systems are affected *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Use workaround - see Local Fix *
**************************************************************** |
| Local Fix: |
Use the "-memsets" option of the db2pd command to determine the
correct memory set size |
| Solution |
Problem first fixed in DB2 Version 9.7 Fix Pack 10 |
| Workaround |
see Local Fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.03.2014
24.11.2014
24.11.2014 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.10
|
 |
