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

FAILURE TO ALLOCATE SHM SEGMENT WITH HUGE PAGES MIGHT END UP WITH TRAP OR
INCORRECT BEHAVIOR

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
This will happen only with Huge Pages being configured. If a
Shared Memory segment allocation fails
with ENOMEM due to Huge Page / Memory shortage the engine
(db2sysc) might trap or misbehave.

The db2diag.log would typically show 2 entries at least. First
one would be the 'watchdog' reporting
the failure to allocate memory, then would come the db2sysc
message. Example:

  2016-12-14-09.50.13.539852-300 I162525E737           LEVEL:
Error (OS)
  PID     : 31569                TID : 46912845637376  PROC :
db2wdog 7 [srv1]
  INSTANCE: srv1               NODE : 007
  HOSTNAME: labonnecuisine
  EDUID   : 2                    EDUNAME: db2wdog 7 [srv1]
  FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog,
probe:9330
  MESSAGE : ZRC=0x820F0002=-2112946174=SQLO_INV_MEM "Invalid
memory addr"
            DIA8561C A invalid memory block was encountered.
  CALLED  : OS, -, shmget                           OSERR:
ENOMEM (12)
  DATA #1 : String, 38 bytes
  Failure getting shared memory segment.
  DATA #2 : Shared memory key, PD_TYPE_SHM_KEY, 4 bytes
  0
  DATA #3 : Shared memory flags, PD_TYPE_SHM_FLAGS, 4 bytes
  3969

Followed by:

  2016-12-14-09.50.13.551682-300 E163263E613           LEVEL:
Error
  PID     : 31579                TID : 46912988243712  PROC :
db2sysc 7
  INSTANCE: srv1               NODE : 007            DB   :
casserole
  APPHDL  : 0-56                 APPID: *N0.srv1.161214144954
  AUTHID  : SRV1               HOSTNAME: labonnecuisine
  EDUID   : 225                  EDUNAME: db2agntp (srv1) 7
  FUNCTION: DB2 UDB, SQO Memory Management, sqloRequestShmget,
probe:11756
  MESSAGE : ZRC=0xFFFFFBEE=-1042
            SQL1042C  An unexpected system error occurred.

Later followed possibly by a trap like this (only upper
functions matter here):

  0x00000000004223A4 __intel_new_memset + 0x0a64
  0x00002AAAAEB1FE20 sqloGetMemChunks + 0x0400
  0x00002AAAAEC133CB sqlpIncreaseLockList + 0x014b
  0x00002AAAAEC126D7 sqlplitP8sqeAgent + 0x0b37
  0x00002AAAAEC0331E sqlpInitLockingComponents + 0x003e
  0x00002AAAAEC0197C sqlpinit + 0x01dc
  0x00002AAAADC23D6C address: 0x00002AAAADC23D6C ;
  0x00002AAAADC1D62B sqeLocalDatabase::FirstConnect + 0x1aab
  0x00002AAAADC0CFE9 sqeDBMgr::StartUsingLocalDatabase + 0x15b9
  0x00002AAAADBBF72E sqeApplication::AppStartUsing + 0x04be
  0x00002AAAADBBE9C4 sqleSubAgentStartUsing + 0x03b4
  0x00002AAAADBBCFB9 sqeApplication::AppSecondaryStartUsing +
0x0409
  0x00002AAAADB9F294 sqeAgent::initSubAgent + 0x1e94
  0x00002AAAADB7D01A sqleProcessSubRequest + 0x02ba
  0x00002AAAADB98580 sqeAgent::RunEDUEv + 0x04a0
  0x00002AAAAF37E047 sqzEDUObj::EDUDriverEv + 0x00f7
  0x00002AAAAEB57181 sqloEDUEntry + 0x0301
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.1 FP2 or later                                 *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT18513 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.10.2017
13.10.2017
13.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)