|
Problem IC96608
|
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 / A50 - 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 users who have set DB2 registry DB2TCP_CLIENT_CONTIMEOUT *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Federation Server V10.5FP3. *
**************************************************************** |
| Local Fix: |
Set ConnectTimeout using db2cli.ini instead
of registry variable DB2TCP_CLIENT_CONTIMEOUT. |
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
The problem is firstly fixed in Federation Server V10.5FP3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.10.2013
27.02.2014
27.02.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
