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 IC78638 Status: Closed

MEMORY ALLOCATION FAILURE DURING DATABASE ACTIVATION RESULTING IN INSTANCE
ABEND IN SQLBTERMBUFFERPOOL

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
When a memory allocation failure occurs during a database 
activation, SQL1224N will be returned, and the instance will be 
brought down, instead of the expected graceful SQL10003C which 
would not cause an instance abend. The following symptoms will 
be seen: 
 
db2diag.log 
=========== 
2011-09-13-11.42.48.042813-240 I8461E573           LEVEL: Error 
PID     : 2768                 TID  : 47927577798976PROC : 
db2sysc 
INSTANCE: db2inst1             NODE : 000          DB   : TEST 
APPHDL  : 0-7                  APPID: 
*LOCAL.db2inst1.110913154221 
AUTHID  : DB2INST1 
EDUID   : 16                   EDUNAME: db2agent (SAMPLE) 
FUNCTION: DB2 UDB, buffer pool services, 
sqlbAllocateAndInitHashTable, probe:40 
MESSAGE : ZRC=0x8B0F0010=-1961951216=SQLO_NOMEM_BPH 
          "No memory available in 'Buffer Pool Heap'" 
          DIA8300C A memory heap error has occurred. 
 
2011-09-13-11.44.24.006867-240 I9035E623           LEVEL: Severe 
PID     : 2768                 TID  : 47927577798976PROC : 
db2sysc 
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE 
APPHDL  : 0-7                  APPID: 
*LOCAL.db2inst1.110913154221 
AUTHID  : DB2INST1 
EDUID   : 16                   EDUNAME: db2agent (SAMPLE) 
FUNCTION: DB2 UDB, buffer pool services, sqlbinit, probe:460 
MESSAGE : ZRC=0x8B0F0010=-1961951216=SQLO_NOMEM_BPH 
          "No memory available in 'Buffer Pool Heap'" 
          DIA8300C A memory heap error has occurred. 
DATA #1 : String, 40 bytes 
Hidden bufferpools initialization failed 
 
2011-09-13-11.44.24.007485-240 I10214E1879         LEVEL: Severe 
PID     : 2768                 TID  : 47927577798976PROC : 
db2sysc 
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE 
APPHDL  : 0-7                  APPID: 
*LOCAL.db2inst1.110913154221 
AUTHID  : DB2INST1 
EDUID   : 16                   EDUNAME: db2agent (SAMPLE) 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, probe:10 
MESSAGE : Possible memory corruption detected. 
 
trap file 
========= 
EDU name     : db2agent (SAMPLE) 
Signal #11 
 
<StackTrace> 
sqloCrashOnCriticalMemoryValidationFailure 
SQLO_MEM_POOL::diagnoseMemoryCorruptionAndCrash 
sqloDiagnoseFreeBlockFailure 
sqlofmblkEx 
sqlofmblk 
sqlbTermBufferPool 
sqlbinit 
sqledint 
sqeLocalDatabase::FirstConnect
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* see APAR description                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* see APAR description                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB 9.5 Fix Pack 9                            * 
****************************************************************
Local Fix:
Ensure there are no memory allocation errors during a database 
startup. The error (SQLO_NOMEM_BPH) is a consequence of a 
misconfigured operating system (shared memory kernel 
configuration parameters too low), or a lack of real memory.
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 UDB 9.5 Fix Pack 9
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC78664 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.09.2011
08.03.2012
08.03.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList