|
Problem IC79463
|
Status: Closed |
CLI ATTRIBUTE SQL_ATTR_CONNECT_NODE DOES NOT WORK WHEN DB2CONNECT_IN_APP_PROCESS=NO IS SET |
| product: |
DB2 CONNECT / DB2CONNCT / 950 - DB2 |
| 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. |
| Problem Summary: |
****************************************************************
* 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: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The problem is first fixed in DB2 Version 9.5 Fix Pack 9 and all
subsequent Fix Packs. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.10.2011
09.03.2012
09.03.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.9
|
 |
