DB2 may crash if critical IPC resources removed by other commands or OS
In case critical IPC resources are removed, DB2 may crash and FODC_Panic may be generated.
As an example, see the following messages in db2diag.log which eventually lead to DB2 panic.
<timestamp> LEVEL: Severe (OS)
PID : 12345 TID : 12345 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 12 EDUNAME: db2thcln 0
FUNCTION: DB2 UDB, oper system services, sqloWaitEDUWaitPost, probe:100
MESSAGE : ZRC=0x8300002B=-2097151957
CALLED : OS, -, semop OSERR: EIDRM (43)
DATA #1 : timeout value, 4 bytes
The above error indicates the critical IPC resource has been removed by external commands,
typically by OS, or cluster managing software etc. This caused various
EDUs in db2 to abort and lead to DB2 panic eventually.
Diagnosing The Problem
Search in OS log for related messages that cause the above error.
Resolving The Problem
Consult with OS Administrator why IPC resource is removed.
16 June 2018