|
Problem IC91776
|
Status: Closed |
AFTER UPGRADING TO V9.7 FP7, QUERY DRDA NICKNAME WILL FAIL IF DB2 REGISTRY DB2TCP_CLIENT_CONTIMEOUT IS SET |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
'db2set -all' command shows DB2TCP_CLIENT_CONTIMEOUT is set.
If federated server option DB2_TWO_PHASE_COMMIT is set to 'Y'
# db2 "select * from schema1.nickname1"
SQL30080N A communication error "-3" occurred sending or
receiving data from the remote database. SQLSTATE=08001
If federated server option DB2_TWO_PHASE_COMMIT is set to 'N'
# db2 "select * from schema1.nickname1"
SQL1042C An unexpected system error occurred. SQLSTATE=58004 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* The user is running drda wrapper. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Federation Server v10.1 fp3. *
**************************************************************** |
| Local Fix: |
Set ConnectTimeout using db2cli.ini instead
of registry variable DB2TCP_CLIENT_CONTIMEOUT. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
The problem was firstly fixed on Federation Server v10.1 fp3. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC96608
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.04.2013
03.10.2013
03.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
