Symptom
DB2 instance crashes with FODC trap.
db2diag.log shows errors as below:
2020-01-01-01.00.00.000000+120 E65115437A3417 LEVEL: Severe (OS)
PID : 12345 TID : 11111 PROC : db2sysc 0
INSTANCE: db2sid NODE : 000 DB : SID
APPHDL : 0-01 APPID: 127.0.0.1.65003.210713032808
AUTHID : SAPSID HOSTNAME: systemname
EDUID : 39813 EDUNAME: db2agent (SID) 0
FUNCTION: DB2 UDB, SQO Latch Tracing, SQLO_SLATCH_CAS64::releaseConflict, probe:330
MESSAGE : ZRC=0x870F011E=-2029059810=SQLO_LATCH_ERROR_EXPECTED_HELD
"expected latch to be held."
CALLED : OS, -, unspecified_system_function
DATA #1 : String, 39 bytes
Attempting to unlock an invalid latch:
Additional errors seen:
MESSAGE : ZRC=0x870F00FB=-2029059845=SQLO_SLATCH_ERROR_HELDX_WITH_SHARED_HOLDERS
"shared latch found with both exclusive and shared holders. Latch likely corrupt."
Read more...
Environment
DB2 10.5 FP6 and lower
Keywords
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.