DB2 - Problembeschreibung
Problem IC79260 | Status: Geschlossen |
DB2 MAY NOT PERFORM OPTIMALLY ON LARGE 64-BIT WINDOWS ENVIRONMENTS DUE TO USE OF MEM_TOP_DOWN FLAG | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
DB2 uses the MEM_TOP_DOWN flag for many memory allocations (VirtualAlloc API) on the Windows platform. The use of this flag causes memory allocations to take longer as the number of allocations gets larger. The MEM_TOP_DOWN flag is used primarily to avoid address space fragmentation in 32-bit environments, and is not needed with 64-bit, so its use will be restricted to 32-bit DB2. The symptom may be particularly noticable when initializing large bufferpools. A workaround exists, that is to set the following internal registry variable: db2set DB2_MEMALLOCATE_HIGH=NO The instance must be recycled with db2stop; db2start | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 running in large Windows environments * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 6 * **************************************************************** | |
Local-Fix: | |
db2set DB2_MEMALLOCATE_HIGH=NO The instance must be recycled with db2stop; db2start | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Lösung | |
Problem first fixed in DB2 Version 9.7 Fix Pack 6 | |
Workaround | |
See Local Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC84204 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 18.10.2011 12.06.2012 12.06.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP6 | |
Problem behoben lt. FixList in der Version | |
9.7.0.6 |