IBM Support

DB2 Panic due to IPC resources removed

Troubleshooting


Problem

DB2 may crash if critical IPC resources removed by other commands or OS

Symptom

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
HOSTNAME: host1
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
-1

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Recovery - Crash Recovery","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"10.1;10.5;9.7;9.8","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
15 June 2026

UID

swg21982543

Page Feedback