home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC62921 Status: Closed

INCORRECT CONFIGURED/MAX SIZES FOR SOME MEMORY HEAPS IN SNAPSHOTS
AND MEMORY TRACKER OUTPUT

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The configured sizes of a number of heaps in monitor snapshot 
output are extremely large. 
 
Node number    = 0 
Memory Pool Type          = Package Cache Heap 
Current size (bytes)          = 589824 
High water mark (bytes)         = 589824 
Configured size (bytes)         = 12884901888 
 
Node number    = 0 
Memory Pool Type          = Catalog Cache Heap 
Current size (bytes)  = 65536 
High water mark (bytes)         = 65536 
Configured size (bytes)          = 12884901888 
 
Node number     = 0 
Memory Pool Type           = Buffer Pool Heap 
Secondary ID               = 1 
Current size (bytes)   = 481230848 
High water mark (bytes)          = 481230848 
Configured size (bytes)     = 12884901888 
 
The memory tracker tool, db2mtrk, also displays these large 
values as maximum values for the heaps.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All.                                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The configured / max sizes for some memory heaps are         * 
* displayed as large values in snapshot monitor and memory     * 
* tracker output.                                              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fixpack 1 or higher                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
This issue was fixed in DB2 V9.7 Fixpack 1. The configured/max 
sizes for memory heaps displayed in monitor snapshot and memory 
tracker output will now correspond to the configured values 
plussome overhead.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.09.2009
23.02.2010
23.02.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList