|
Problem IC96608
|
Status: Geschlossen |
AFTER UPGRADING TO V9.7 FP7, QUERY DRDA NICKNAME WILL FAIL IF DB2 REGISTRY DB2TCP_CLIENT_CONTIMEOUT IS SET |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problembeschreibung: |
'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-Zusammenfassung: |
****************************************************************
* 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. |
| verfügbare FixPacks: |
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
|
| Lösung |
The problem is firstly fixed in Federation Server V10.5FP3. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 03.10.2013
27.02.2014
27.02.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
