|
Problem IC76998
|
Status: Geschlossen |
DB2TCP_CLIENT_RCVTIMEOUT IS SET TO 0 IF YOU ISSUE CONNECT STATEM ENT FOR MULTIPLE TIMES WITHOUT DISCONNECT OR CONNECT RESET. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problembeschreibung: |
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. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All users of version 9.5 on Linux, Unix and Windows *
* platforms. *
****************************************************************
* PROBLEM DESCRIPTION: *
* 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. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB Version 9.5 FixPak 9 or higher levels. *
**************************************************************** |
| Local-Fix: |
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. |
| verfügbare FixPacks: |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
First fixed in DB2 UDB Version 9.5 FixPak 9. |
| Workaround |
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. |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC79572
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 16.06.2011
12.03.2012
12.03.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.0.,
9.5.
|
| Problem behoben lt. FixList in der Version |
| 9.5.0.9
|
 |
