home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC65447 Status: Geschlossen

DB2 fails to allocate memory when DB2_LARGE_PAGE_MEM=* config parameter
is set on Windows server.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
DB2_LARGE_PAGE_MEM=* is set in Windows 2003 ENT SVR 64bit to use 
large page memory, hit the OSERR(87) "The parameter is 
incorrect." and DIA8300C A memory heap error has occurred. 
 
CALLED  : OS, -, VirtualAlloc 
OSERR   : 87 "The parameter is incorrect." 
MESSAGE : Private memory and/or virtual address space exhausted 
DATA #1 : Requested size, PD_TYPE_MEM_REQUESTED_SIZE, 8 bytes 
65536 
DATA #2 : Current set size, PD_TYPE_SET_SIZE, 8 bytes 
128974848 
 
FUNCTION: DB2 UDB, buffer pool services, sqlbinit, probe:500 
MESSAGE : ZRC=0x8B0F0010=-1961951216=SQLO_NOMEM_BPH 
          "No memory available in 'Buffer Pool Heap'" 
          DIA8300C A memory heap error has occurred. 
DATA #1 : String, 35 bytes 
BufferPool memory allocation failed 
 
Windows API VirtualAlloc is requesed to allocate memory of size 
64KB with flag MEM_LARGE_PAGES. 
This is a non-standard allocation and the API fails with an 
error "The parameter is incorrect."
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2_LARGE_PAGE_MEM=* is set in Windows 2003 ENT SVR 64bit    * 
* touse large page memory, hit the OSERR(87) "The parameter    * 
* isincorrect." and DIA8300C A memory heap error has           * 
* occurred.CALLED  : OS, -, VirtualAllocOSERR  : 87 "The       * 
* parameter is incorrect."MESSAGE : Private memory and/or      * 
* virtual address spaceexhaustedDATA #1 : Requested size,      * 
* PD_TYPE_MEM_REQUESTED_SIZE, 8bytes65536DATA #2 : Current set * 
* size, PD_TYPE_SET_SIZE, 8 bytes128974848FUNCTION: DB2 UDB,   * 
* buffer pool services, sqlbinit, probe:500MESSAGE :           * 
* ZRC=0x8B0F0010=-1961951216=SQLO_NOMEM_BPH"No memory          * 
* available in 'Buffer Pool Heap'"DIA8300C A memory heap error * 
* has occurred.DATA #1 : String, 35 bytesBufferPool memory     * 
* allocation failed                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to product version 9.7 Fix Pack 2.                   * 
****************************************************************
Local-Fix:
remove DB2_LARGE_PAGE_MEM=* registry for work around
verfügbare FixPacks:
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 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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

Lösung
Problem was fixed in version 9.7 Fix Pack 2. 
We are using the flag MEM_LARGE_PAGES to get 64kb of memory, 
 
 
 
which is the root cause for the failure. 
We didn't want to use large page flag, which could cause 
 
 
 
problem to use the thread model.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.01.2010
14.06.2010
14.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList