| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC91618 | Status: Closed |
NULL VALUES OR EMPTY STRINGS IN MON_GET_MEMORY_POOL() COLUMN MEMORY_POOL_TYPE | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
A SELECT using MON_GET_MEMORY_POOL() can return NULL values or
empty strings for MEMORY_POOL_TYPE as not all existing memory
pool types are externatlized yet.
For example:
select current_timestamp, member, MEMORY_SET_TYPE,
MEMORY_POOL_TYPE, MEMORY_POOL_ID, APPLICATION_HANDLE, ED
U_ID, MEMORY_POOL_USED FROM
TABLE(SYSPROC.MON_GET_MEMORY_POOL(NULL, '', -2)) where
MEMORY_POOL_TYPE is null or MEMORY_POOL_TYPE =
''"
may return:
2013-04-15-16.25.42.812245 0 PRIVATE
90
- 44129 0
MEMORY_POOL_ID = 90 is not externalized yet, therefore no
MEMORY_POOL_TYPE is printed out. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 9. * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
| Solution | |
First fixed in DB2 Version 9.7 Fix Pack 9. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.04.2013 17.12.2013 17.12.2013 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP9 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.9 |
|
| 9.7.0.9 |
|