DB2 - Problembeschreibung
Problem IC89914 | 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 / 970 - 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 and * * DB2TCP_CLIENT_CONTIMEOUT is set. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 or Federation Server V97FP9. * **************************************************************** | |
Local-Fix: | |
Set ConnectTimeout using db2cli.ini instead of registry variable DB2TCP_CLIENT_CONTIMEOUT. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
Lösung | |
The problem is firstly fixed on DB2 or Federation Server V97FP9. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC91776 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 30.01.2013 17.12.2013 17.12.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP9 | |
Problem behoben lt. FixList in der Version | |
9.7.0.9 | |
9.7.0.9 |