Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC91776 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 / A10 - 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 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.
verfügbare FixPacks:
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

Lösung
The problem was firstly fixed on Federation Server v10.1 fp3.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC96608 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.04.2013
03.10.2013
03.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList