DB2 FOR LUW / DB2FORLUW / 970 - DB2

On DB2 client side, when application closes a TCP/IP connection 
that is connected to remote DB2 server, a "Detected client 
termination" error might be reported in db2diag.log file on DB2 
server side. 
 
Here is an example of the error on DB2 server side: 
=========================================== 
2014-01-01-01.01.01.123456+123 I224964E544         LEVEL: Error 
PID     : 12345                TID  : 12345678901234PROC : 
db2sysc 2 
INSTANCE: db2inst1             NODE : 002          DB   : SAMPLE 
APPHDL  : 12-345               APPID: 
10.12.34.56.78901.140315123456 
AUTHID  : DB2INST1 
EDUID   : 123                  EDUNAME: db2agent (SAMPLE) 2 
FUNCTION: DB2 UDB, common communication, sqlcctcptest, probe:11 
MESSAGE : Detected client termination 
DATA #1 : Hexdump, 2 bytes 
0x00002AB15C3F3A88 : 3600 
6. 
 
2014-01-01-01.01.01.123457+480 I225509E526         LEVEL: Error 
PID     : 12345                TID  : 12345678901234PROC : 
db2sysc 2 
INSTANCE: db2inst1             NODE : 002          DB   : SAMPLE 
APPHDL  : 12-345               APPID: 
10.12.34.56.78901.140315123456 
AUTHID  : DB2INST1 
EDUID   : 123                  EDUNAME: db2agent (SAMPLE) 2 
FUNCTION: DB2 UDB, common communication, sqlcctest, probe:50 
MESSAGE : sqlcctest RC 
DATA #1 : Hexdump, 2 bytes 
0x00002AB15C3F3AC0 : 3600 
6. 
 
2014-01-01-01.01.01.123458+480 I226036E506         LEVEL: Error 
PID     : 12345                TID  : 12345678901234PROC : 
db2sysc 2 
INSTANCE: db2inst1             NODE : 002          DB   : SAMPLE 
APPHDL  : 12-345               APPID: 
10.12.34.56.78901.140315123456 
AUTHID  : DB2INST1 
EDUID   : 123                  EDUNAME: db2agent (SAMPLE) 2 
FUNCTION: DB2 UDB, base sys utilities, 
sqeAgent::AgentBreathingPoint, probe:10 
CALLED  : DB2 UDB, common communication, sqlcctest 
RETCODE : ZRC=0x00000036=54 
=========================================== 
 
The problem was introduced in DB2 LUW Version 9.7 Fix Pack 9. It 
doesn't exist in Version 9.7 levels prior to Fix Pack 9. 
 
The problem exists in Database Partitioned Feature (DPF) 
environment only. It doesn't exist in single-node environment.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 9.7 DPF environment on Linux, Unix and  * 
* Windows platforms.                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 LUW Version 9.7 Fix Pack 10 or higher levels.  * 
****************************************************************

The problem can be avoided by setting DB2 registry variable 
DB2CHECKCLIENTINTERVAL=0 on DB2 server side. 
Please note the DB2 server instance must be recycled to pick up 
the change on the registry variable.

First fixed in DB2 LUW Version 9.7 Fix Pack 10.

The problem can be avoided by setting DB2 registry variable 
DB2CHECKCLIENTINTERVAL=0 on DB2 server side. 
Please note the DB2 server instance must be recycled to pick up 
the change on the registry variable.

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

05.05.2014
10.11.2014
10.11.2014

9.7.FP10