DB2 FOR LUW / DB2FORLUW / 970 - DB2

If you issued CONNECT statement multiple times without any 
DISCONNECT or CONNECT RESET between them, DB2's registry 
variable DB2TCP_CLIENT_RCVTIMEOUT would be set to 0 ever since 
the 2nd time of CONNECT statement. 
 
This problem only happens when both DB2TCP_CLIENT_RCVTIMEOUT and 
DB2TCP_CLIENT_CONTIMEOUT are enabled.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 9.7 on Linux, Unix and Windows          * 
* platforms.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.7 FixPak 6 or higher levels.    * 
****************************************************************

1. Starting from the 2nd CONNECT statement, issue DISCONNECT or 
CONNECT RESET statement prior to CONNECT statement. 
2. Use DB2TCP_CLIENT_RCVTIMEOUT only, do not use registry 
variable DB2TCP_CLIENT_CONTIMEOUT.

DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First fixed in DB2 UDB Version 9.7 FixPak 6.

1. Starting from the 2nd CONNECT statement, issue DISCONNECT or 
CONNECT RESET statement prior to CONNECT statement. 
2. Use DB2TCP_CLIENT_RCVTIMEOUT only, do not use registry 
variable DB2TCP_CLIENT_CONTIMEOUT.

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

01.11.2011
12.06.2012
12.06.2012

9.7.