Symptom
Database crashes with signal 11 at function call sqlrwFilteredTableIterator.
1. The database log (db2diag.log) shows the following:
2023-05-08-22.28.43.480949+060 I224537255E657 LEVEL: Severe
PID : 23287 TID : 140140320122624 PROC : db2sysc 0
INSTANCE: db2abc NODE : 000 DB : abc
APPHDL : 0-62672 APPID: *LOCAL.db2abc.230509210413
UOWID : 46 ACTID: 1
AUTHID : DB2abc HOSTNAME: abcdef123456
EDUID : 61533 EDUNAME: db2agent (abc) 0
FUNCTION: DB2 UDB, RAS/PD component, pdResilienceIsSafeToSustain, probe:800
DATA #1 : String, 37 bytes
Trap Sustainability Criteria Checking
DATA #2 : Hex integer, 8 bytes
0x0000000400041040
DATA #3 : Boolean, 1 bytes
false
2023-05-08-22.28.45.071820+060 I224545221E1078 LEVEL: Severe
PID : 23287 TID : 140140320122624 PROC : db2sysc 0
INSTANCE: db2abc NODE : 000 DB : abc
APPHDL : 0-62672 APPID: *LOCAL.db2abc.230509210413
UOWID : 46 ACTID: 1
AUTHID : DB2abc HOSTNAME: abcdef123456
EDUID : 61533 EDUNAME: db2agent (abc) 0
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:250
MESSAGE : ZRC=0x87120007=-2028863481=SQLR_SEVERE_PGM_ERROR
"Severe programming error"
DIA8516C A severe internal processing error has occurred.
2023-05-08-22.28.45.178373+060 I224548391E652 LEVEL: Severe
PID : 23287 TID : 140140320122624 PROC : db2sysc 0
INSTANCE: db2abc NODE : 000 DB : abc
APPHDL : 0-62672 APPID: *LOCAL.db2abc.230509210413
UOWID : 46 ACTID: 1
AUTHID : DB2abc HOSTNAME: abcdef123456
EDUID : 61533 EDUNAME: db2agent (abc) 0
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:500
MESSAGE : * NOTE: NULL pentptr ... no creator/package data
DATA #1 : Hexdump, 1 bytes
0x00007FF03072B813 : 2A
2023-05-08-22.28.46.031955+060 I224559488E628 LEVEL: Severe
PID : 23287 TID : 140140320122624 PROC : db2sysc 0
INSTANCE: db2abc NODE : 000 DB : abc
APPHDL : 0-62672 APPID: *LOCAL.db2abc.230509210413
UOWID : 46 ACTID: 1
AUTHID : DB2abc HOSTNAME: abcdef123456
EDUID : 61533 EDUNAME: db2agent (abc) 0
FUNCTION: DB2 UDB, index manager, sqldDumpDKEY, probe:5
MESSAGE : The key pointer is invalid:
DATA #1 : Hexdump, 8 bytes
0x00007F74F501E6A8 : 0000 0000 0000 0000
2023-05-08-22.28.46.192623+060 I224561798E613 LEVEL: Severe
PID : 23287 TID : 140140320122624 PROC : db2sysc 0
INSTANCE: db2abc NODE : 000 DB : abc
APPHDL : 0-62672 APPID: *LOCAL.db2abc.230509210413
UOWID : 46 ACTID: 1
AUTHID : DB2abc HOSTNAME: abcdef123456
EDUID : 61533 EDUNAME: db2agent (abc) 0
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary logging function), probe:30
MESSAGE : SQLD_TCB:
DATA #1 : String, 38 bytes
Perm Table(5:5)=SYSTOOLS.HMON_ATM_INFO
2023-05-08-22.29.16.087234+060 E225221720E1665 LEVEL: Severe
PID : 23287 TID : 140140320122624 PROC : db2sysc 0
INSTANCE: db2abc NODE : 000 DB : abc
APPHDL : 0-62672 APPID: *LOCAL.db2abc.230509210413
UOWID : 46 ACTID: 1
AUTHID : DB2abc HOSTNAME: abcdef123456
EDUID : 61533 EDUNAME: db2agent (abc) 0
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, probe:90
MESSAGE : ADM14011C A critical failure has caused the following type of error:
"Trap". The database manager cannot recover from the failure. First
Occurrence Data Capture (FODC) was invoked in the following mode:
"Automatic". FODC diagnostic information is located in the following
directory:
"/db2/abc/db2dump/FODC_AppErr_2023-05-08-22.28.45.042154_23287_61533_
000/".
DATA #1 : Signal Number Recieved, 4 bytes
11
2023-05-08-22.29.27.233600+060 E225226156E608 LEVEL: Severe
PID : 23285 TID : 140164596754176 PROC : db2wdog 0 [db2abc]
INSTANCE: db2abc NODE : 000
HOSTNAME: abcdef123456
EDUID : 2 EDUNAME: db2wdog 0 [db2abc]
FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog, probe:20
MESSAGE : ADM0503C An unexpected internal processing error has occurred. All
database manager processes associated with this instance have been
shutdown. Diagnostic information has been recorded. Contact IBM
Support for further assistance.
2. Stack trace inside the trap file under FODC dump directory.
DB2 build information: DB2 v11.5.5.0 s2011011400 SQL11055
instance name: db2abc.000
EDU name : db2agent (abc) 0 [-]
EDU ID : 61533
Signal #11
------FUNCTION + OFFSET------
sqloEDUCodeTrapHandler + 0x03a9
address: 0x00007FF034EB1CE0 ; dladdress: 0x00007FF034EA0000 ; offset in lib: 0x0000000000011CE0 ;
_ZN26sqlrwFilteredTableIterator7executeEv + 0x0269
_Z20sqlrwGetIndexMetricsP8sqlrr_cbP24sqlrwGetIndexMetricsArgsPPvPl + 0x01e2
_Z30sqlrwGetWLMTableFunctionResultP8sqlrr_cbP20sqlrw_rpc_tf_requestPPvPlbP19SQLR_BDSREPLY_STATE + 0x023b
_Z36sqlrwGetWLMTableFunctionMergedResultjPPv + 0x0261
_Z29sqlerTrustedRtnCallbackRouterjPPv + 0x0d4b
monGetIndex_v115m4fp0 + 0x06a7
sqloInvokeFnArgs + 0x114d
Read more...
Environment
- SAP on IBM Db2 for Linux, UNIX, and Windows
- IBM Db2 11.5 with version lower than Db2 11.5.5.1.
Product
Keywords
crash, signal 11, sqlrwFilteredTableIterator, sqlrwGetIndexMetrics, sqlrwGetTableMetrics, sqlrwGetWLMTableFunctionResult , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.