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 IC79463 Status: Geschlossen

CLI ATTRIBUTE SQL_ATTR_CONNECT_NODE DOES NOT WORK WHEN
DB2CONNECT_IN_APP_PROCESS=NO IS SET

Produkt:
DB2 CONNECT / DB2CONNCT / 950 - DB2
Problembeschreibung:
The CLI attribute SQL_ATTR_CONNECT_NODE does not get propagated 
to the LUW server if connecting through a gateway or when 
DB2CONNECT_IN_APP_PROCESS=NO is set, the node number gets lost 
on the gateway.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users using CLI attribute SQL_ATTR_CONNECT_NODE          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The CLI attribute SQL_ATTR_CONNECT_NODE does not get         * 
* propagated to the LUW server if connecting through a gateway * 
* or when DB2CONNECT_IN_APP_PROCESS=NO is set, the node number * 
* gets lost on the gateway. This causes the connect attempt is * 
* routed to node 0 instead of the node specified.              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fix Pack 9.                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
The problem is first fixed in DB2 Version 9.5 Fix Pack 9 and all 
subsequent Fix Packs.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
26.10.2011
09.03.2012
09.03.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP9
Problem behoben lt. FixList in der Version
9.5.0.9 FixList