Under a specific timing conditions in DPF enviroment db2start
might be crash due to one of the nodes is slower with the
shutdown process. This issue restricted to Linux platform only.
db2diag.log will contain the following messages:
2012-10-04-17.28.33.710709-240 E28881685E1461 LEVEL: Event
PID : 4421 TID : 46912728197440PROC :
db2syscr
INSTANCE: INSTANCE_NAME NODE : 033
FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:1
START : DB2 DBM
...
2012-10-04-17.28.34.057517-240 E28884609E381 LEVEL: Error
(OS)
PID : 4460 TID : 46912728197440PROC :
db2sysc 33
INSTANCE: INSTANCE_NAME NODE : 033
EDUID : 1 EDUNAME: db2sysc 33
FUNCTION: DB2 UDB, SQO Memory Management,
sqloMemCreateSingleSegment, probe:100
CALLED : OS, -, shmget OSERR: EEXIST
(17)
...
2012-10-04-17.28.34.751221-240 E28888705E1506 LEVEL: Severe
(OS)
PID : 3391 TID : 46912716909280PROC :
db2star2
INSTANCE: INSTANCE_NAME NODE : 033
FUNCTION: DB2 UDB, oper system services, sqloWaitIPCWaitPost,
probe:100
MESSAGE : ZRC=0x8300002B=-2097151957
CALLED : OS, -, msgrcv OSERR: EIDRM
(43)
...
2012-10-04-17.28.34.808998-240 E28890987E513 LEVEL: Error
(OS)
PID : 4461 TID : 46912728197440PROC :
db2ckpwd 33
INSTANCE: INSTANCE_NAME NODE : 033
EDUID : 1 EDUNAME: db2sysc 33
FUNCTION: DB2 UDB, oper system services, sqlorqueInternal,
probe:9
MESSAGE : ZRC=0x870F003E=-2029060034=SQLO_QUE_BAD_HANDLE "Bad
Queue Handle"
DIA8555C An invalid message queue handle was
encountered.
CALLED : OS, -, msgrcv OSERR: EINVAL
(22)
...
2012-10-04-17.28.35.362569-240 I28908507E826 LEVEL:
Warning
PID : 4421 TID : 46912728197440PROC :
db2wdog 33
INSTANCE: INSTANCE_NAME NODE : 033
EDUID : 2 EDUNAME: db2wdog 33
FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog, probe:10
MESSAGE : ZRC=0x820F0003=-2112946173=SQLO_MEM_ERROR "General Mem
Mgt error"
DIA8300C A memory heap error has occurred.
DATA #1 : String, 34 bytes
Unable to connect to new segments.
...
2012-10-04-17.28.35.665578-240 E28913013E290 LEVEL: Error
PID : 4421 TID : 46912728197440PROC :
db2wdog 33
INSTANCE: INSTANCE_NAME NODE : 033
EDUID : 2 EDUNAME: db2wdog 33
FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog, probe:190
...
2012-10-04-17.28.36.572630-240 I28923941E346 LEVEL: Severe
PID : 4421 TID : 46912728197440PROC :
db2wdog 33
INSTANCE: INSTANCE_NAME NODE : 033
EDUID : 2 EDUNAME: db2wdog 33
FUNCTION: DB2 UDB, base sys utilities, sqleCleanupResources,
probe:7
MESSAGE : Cleaning up ipc resources and exiting.
...
2012-10-04-17.28.37.064055-240 E28928501E2185 LEVEL: Severe
(OS)
PID : 4460 TID : 46912728197440PROC :
db2sysc 33
INSTANCE: INSTANCE_NAME NODE : 033
EDUID : 11 EDUNAME: db2sysc 33
FUNCTION: DB2 UDB, SQO Latch Tracing,
SQLO_SLATCH_CAS64::getConflictComplex, probe:200
CALLED : OS, -, unspecified_system_function OSERR: EIDRM
(43)
...
2012-10-04-17.28.37.076378-240 E28930687E780 LEVEL:
Critical
PID : 4460 TID : 46912728197440PROC :
db2sysc 33
INSTANCE: INSTANCE_NAME NODE : 033
EDUID : 11 EDUNAME: db2sysc 33
FUNCTION: DB2 UDB, base sys utilities, sqle_panic, probe:10
MESSAGE : ADM14001C An unexpected and critical error has
occurred: "Panic".
The stack at the time of the failure should look like this:
sqlo_waitlist::markPostPending
sqloResetEDUWaitHandle
sqloInitializeEDUWaitHandle
sqlockpw_daemon_term
libdb2e.so.1
sqloRunInstance
DB2main
sqloEDUMainEntryPcj
sqloEDUEntry
libpthread-2.5.so
clone |
