db2diag 내용 |
2012-03-03-10.19.17.180938+540 I14553178A429 LEVEL: Error PID : 1503276 TID : 2057 PROC : db2sysc 0 INSTANCE: db2inst NODE : 000 EDUID : 2057 EDUNAME: db2tcpcm 0 FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:155 MESSAGE : DIA3208E Error encountered in TCP/IP protocol support. TCP/IP function "close". Socket was "7". Errno was "9".
2012-03-03-10.19.17.209826+540 I14554715A343 LEVEL: Error PID : 1368240 TID : 1 PROC : db2fmp (idle) 0 INSTANCE: db2inst NODE : 000 EDUID : 1 EDUNAME: db2fmp (idle) 0 FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3 RETCODE : ZRC=0x83000024=-2097151964
2012-03-03-10.19.17.210162+540 I14555059A458 LEVEL: Error PID : 1368240 TID : 1 PROC : db2fmp (idle) 0 INSTANCE: db2inst NODE : 000 EDUID : 1 EDUNAME: db2fmp (idle) 0 FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpListener, probe:999 MESSAGE : FMP exiting with error. Last agent registered: DATA #1 : Hexdump, 4 bytes 0x0FFFFFFFFFFFF028 : 0000 0000 ....
|
원인 |
If you encounter this while stopping the instance with db2stop, you probably can ignore it. Your instance probably has more than 1 db2tcpcm process, and after db2stop is issued, these processes simultaneously will try to close the same socket. Only one of them will succeed, the other(s) will fail as the socket is already closed and will write a DIA3208E message to db2diag.log
|
조치 |
You may check the setting of variable DB2TCPCONNMGRS and set it to 1 (using db2set), this should stop the DIA3208E messages.
|
'Troubleshooting' 카테고리의 다른 글
[이중화] DB2 HADR 구성 시, db2haicu 오류 (0) | 2012.12.23 |
---|---|
[SQL0307N] Embedded SQC Pre-Compile 오류 (0) | 2012.12.20 |
[일반] 64-bit Module Load 관련 오류 메시지 (0) | 2012.12.20 |
[SQL] SQL0444N Reason code 4 (built in function) (0) | 2012.12.17 |
[권한] SQL5193N (workload:sysdefaultuserworkload) (0) | 2012.10.15 |