"Detected client termination" in db2diag.log file.

Problem(Abstract)

db2diag.log file may get filled with "Detected client termination" error messages.

Symptom

Following errors may be seen in db2diag.log file.

2012-10-07-03.31.44.562773+480 I559988E520 LEVEL: Error

PID : 2160 TID : 140574011156224PROC : db2sysc 
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE 
APPHDL : 0-4470 APPID: 202.27.30.1.2101.121006192554 
AUTHID : PSOGALAG 
EDUID : 568 EDUNAME: db2agent (SAMPLE) 
FUNCTION: DB2 UDB, common communicati on, sqlcctest, probe:50 
MESSAGE : sqlcctest RC 
DATA #1 : Hexdump, 2 bytes 
0x00007FD9EFFF6780 : 3600 

2012-10-07-03.31.44.543149+480 I560509E538 LEVEL: Error 
PID : 2160 TID : 140574002767616PROC : db2sysc 
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE 
APPHDL : 0-4510 APPID: 202.27.30.1.2286.121006192634 
AUTHID : PSOGALAD 
EDUID : 570 EDUNAME: db2agent (SAMPLE) 
FUNCTION: DB2 UDB, common communication, sqlcctcptest, probe:11 
MESSAGE : Detected client termination 
DATA #1 : Hexdump, 2 bytes 
0x00007FD9EF7F6748 : 3600 

Resolving the problem

Function sqlcctcptest() tests if the client connection is active and function sqlcctest() tests whether the connection is still valid.

If you don't want such messages to be logged into db2diag.log file, you can set DB2CHECKCLIENTINTERVAL to zero.

For Example : Issue following:

1) db2set DB2CHECKCLIENTINTERVAL=0 
2) db2stop 
3) db2start

Note : This variable specifies the frequency of TCP/IP client connection verifications during an active transaction. It permits early detection of client termination, instead of waiting until after the completion of the query. If this variable is set to 0, no verification is performed.

http://www-01.ibm.com/support/docview.wss?uid=swg21613530