When monitor switches are being manipulated through the
db2MonitorSwitches() API, db2 can trap with the following stack
trace:
Stack #1 Signal #11 Timestamp
2016-07-29-01.06.20.606452
0 ossDumpStackTraceInternal
1 ossDumpStackTraceV98
2 OSSTrapFile::dumpEx
3 sqlo_trce
4 sqloEDUCodeTrapHandler
5 _IO_ftrylockfile
6 sqlmonbackend
7 sqlesrvr
8 sqleMappingFnServer
9 sqlerKnownProcedure
10 sqlerCallDL
11 sqljs_ddm_excsqlstt
12 sqljsParseRdbAccessed
13 sqljsParse
14 sqljsSqlam
15 sqljsDriveRequests
16 sqljsDrdaAsInnerDriver
17 sqljsDrdaAsDriver
18 sqeAgent::RunEDU
19 sqzEDUObj::EDUDriver
20 sqloEDUEntry
21 start_thread
22 clone
Diag log
2016-07-29-01.06.20.634590-300 I862983E620 LEVEL:
Error
PID : 27976 TID : 139679194146560 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
APPHDL : 0-960 APPID:
*LOCAL.db2inst1.160729060621
AUTHID : DB2INST1 HOSTNAME: 541067lppldbc1
EDUID : 228 EDUNAME: db2agent (instance) 0
FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh,
probe:2
MESSAGE : Error in agent servicing application with
coor_agent_index:
DATA #1 : Hexdump, 2 bytes
0x00007F099880F6B0 : C003
..
2016-07-29-01.06.20.634742-300 I863604E617 LEVEL:
Error
PID : 27976 TID : 139679194146560 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
APPHDL : 0-960 APPID:
*LOCAL.db2inst1.160729060621
AUTHID : DB2INST1 HOSTNAME: 541067lppldbc1
EDUID : 228 EDUNAME: db2agent (instance) 0
FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh,
probe:3
MESSAGE : Error in agent servicing application with CLIENT PID:
DATA #1 : Hexdump, 5 bytes
0x00007F099880F690 : 3233 3439 36
23496
....
..
2
2016-07-29-01.06.20.635517-300 I867467E626 LEVEL:
Error
PID : 27976 TID : 139679194146560 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
APPHDL : 0-960 APPID:
*LOCAL.db2inst1.160729060621
AUTHID : DB2INST1 HOSTNAME: 541067lppldbc1
EDUID : 228 EDUNAME: db2agent (instance) 0
FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh,
probe:10
MESSAGE : Error in agent servicing application with APPLICATION
NAME:
DATA #1 : Hexdump, 7 bytes
0x000000020552ACBA : 6462 3267 6F76 64
db2govd
2016-07-29-01.06.20.708770-300 I868094E614 LEVEL:
Severe
PID : 27976 TID : 139679194146560 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
APPHDL : 0-960 APPID:
*LOCAL.db2inst1.160729060621
AUTHID : DB2INST1 HOSTNAME: 541067lppldbc1
EDUID : 228 EDUNAME: db2agent (instance) 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
0x0000000400004000
DATA #3 : Boolean, 1 bytes
true
...
2016-07-29-01.06.20.710774-300 E873297E1607 LEVEL:
Severe
PID : 27976 TID : 139679194146560 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
APPHDL : 0-960 APPID:
*LOCAL.db2inst1.160729060621
AUTHID : DB2INST1 HOSTNAME: 541067lppldbc1
EDUID : 228 EDUNAME: db2agent (instance) 0
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler,
probe:80
MESSAGE : ADM14012C A critical failure has caused the following
type of error:
"Trap". The DB2 database manager will attempt to
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:
"/sw/db2diag/FODC_Trap_2016-07-29-01.06.20.606324_0000/".
DATA #1 : Signal Number Recieved, 4 bytes
11
DATA #2 : Siginfo, 128 bytes
0x00007F099880FBF0 : 0B00 0000 0000 0000 0100 0000 0000 0000
................
0x00007F099880FC00 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x00007F099880FC10 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x00007F099880FC20 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x00007F099880FC30 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x00007F099880FC40 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x00007F099880FC50 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x00007F099880FC60 : 0000 0000 0000 0000 0000 0000 0000 0000
................ |
