DB2 tries to free an Inter Process Communications resource twice
which results in the informational messages below:
2010-07-00-08.56.51.048014-240 I42863825A562 LEVEL: Severe
PID : 1233038 TID : 17221 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-25290 APPID: 192.168.10.1.100928133048
AUTHID : db2user
EDUID : 17221 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary
logging func, probe:0
MESSAGE : IPC Semaphore Set ID
DATA #1 : Hexdump, 8 bytes
0x0780000001C2FF6C : FFFF FFFF 0000 0000
........
2010-07-00-08.56.51.048241-240 I42864388A562 LEVEL: Severe
PID : 1233038 TID : 17221 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-25290 APPID: 192.168.10.1.100928133048
AUTHID : db2user
EDUID : 17221 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary
logging
func, probe:0
MESSAGE : Receive Semaphore ID
DATA #1 : Hexdump, 8 bytes
0x0780000001C2FF84 : 0000 0000 0000 0000
........
2010-07-00-08.56.51.048482-240 I42864951A439 LEVEL: Severe
PID : 1233038 TID : 17221 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-25290 APPID: 192.168.10.1.100928133048
AUTHID : db2user
EDUID : 17221 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, common communication, sqlccFreeIPCs, probe:70
RETCODE : ZRC=0xFFFFFFFF=-1
This fix prevents these messages from being falsely returned.
One situation when these messages may appear in your db2diag.log
is when the DBM CFG parameter KEEPFENCED=NO is set. |
