DB2 - Problembeschreibung
Problem IC62921 | Status: Geschlossen |
INCORRECT CONFIGURED/MAX SIZES FOR SOME MEMORY HEAPS IN SNAPSHOTS AND MEMORY TRACKER OUTPUT | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
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 | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 01.09.2009 23.02.2010 23.02.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP1 | |
Problem behoben lt. FixList in der Version | |
9.7.0.1 |