DB2's IPC listener panics when "Queue Shared Memory" is
exhausted. This memory is allocated by DB2 only on the Windows
platform, and is used to support queue messaging for Load, CLP,
as well as transactional types of requests such as local
connection attempts - responded to by the DB2 IPC listener. If
this memory is temporarily exhausted, which may only be for a
short moment in time, it should not cause critical operations to
fail. Rather, they should retry until the resource becomes
available.
db2diag.log message will show the following:
-------------2012-01-17-15.13.59.640000-300 I1190914H444
LEVEL: Severe
PID : 4916 TID : 2596 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000
EDUID : 2596 EDUNAME: db2ipccm 0
FUNCTION: DB2 UDB, common communication, sqlccipc_process_conn,
probe:1
RETCODE : ZRC=0x870F0041=-2029060031=SQLO_QUE_NOT_SENT "Message
Not Sent"
DIA8557C No message was sent using the message queue.
2012-01-17-15.13.59.734000-300 I1191360H435 LEVEL: Severe
PID : 4916 TID : 2596 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000
EDUID : 2596 EDUNAME: db2ipccm 0
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary
logging func, pro
be:0
MESSAGE : TQM Reply Failed
DATA #1 : Hexdump, 4 bytes
0x148EFCF8 : 90FC 8E14 ....
2012-01-17-15.13.59.750000-300 I1191797H334 LEVEL: Severe
PID : 4916 TID : 2596 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000
EDUID : 2596 EDUNAME: db2ipccm 0
FUNCTION: DB2 UDB, common communication, sqlccipcconnmgr_child,
probe:36
RETCODE : ZRC=0x0000004C=76
2012-01-17-15.13.59.765000-300 E1192133H813 LEVEL:
Critical
PID : 4916 TID : 2596 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000
EDUID : 2596 EDUNAME: db2ipccm 0
FUNCTION: DB2 UDB, base sys utilities, sqle_panic, probe:10
MESSAGE : ADM14001C An unexpected and critical error has
occurred: "Panic".
The instance may have been shutdown as a result.
"Automatic" FODC
(First Occurrence Data Capture) has been invoked and
diagnostic
information has been recorded in directory
"D:\sqllib\work\FODC_Panic_2012-01-17-15.13.59.765000_0000\".
Please
look in this directory for detailed evidence about
what happened and
contact IBM support if necessary to diagnose the
problem. |
