home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC87914 Status: Closed

During Xa connect,CLI encounter errors SQL0843N, CLI0119E, when using
different name for dbalias and dsn

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
When customer used "SQLSetConnectAttrw 1 SQL_ATTR_ENLIST_IN_DTC 
1" after sqldriverconnect. CLI_dtcEnlistInTransaction will call 
SQLConnect2 which in turn will call XA to upgrade the existing 
connection. In sqlconnect2 code cli passing wrong dbalias 
(because in first connect i.e sqldriverconnect2(). sqlconnect2() 
call we are swapping dbalias_name with dsn_name. so during XA 
connect instead of sending dbalias for further processing CLI is 
sending dsn_name) for cli_slqconnect() and we encounter above 
errors during setting of accounting information thru sqe api 
sqle_set_info_opt()
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the DB2 Client version to V10 Fix Pack 2 or higher   * 
****************************************************************
Local Fix:
As workaround customer can use same name for both dbalias and 
dsn 
 
Issued is first fixed in v97fp7
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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

Solution
This problem was first fixed in DB2 V10 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2012
11.02.2013
11.02.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList