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 IC93561 Status: Closed

XA connection driven by xa_open gives SQL1013N if commProtocol=TCPIP is
missing in the dsdriver.cfg

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
XA applications which needs a new connection to database do not 
refer db2dsdriver.cfg. 
The application returns SQL1013N if no database catalog is 
available or if the needed information for connection is not 
supplied in the connection string. 
 
V10.5 is aware of the db2dsdriver.cfg in this scenario starting 
in the FixPack 0, however it requires commProtocol keyword in 
the dsncollection section of the db2dsdriver.cfg.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use Data Server driver.                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to V10.5 FixPack 3 or later.                  * 
****************************************************************
Local Fix:
Please add commProtocol keyword to specify communication 
protocol explicitly. 
or 
Please catalog the database if the client supports database 
catalog. 
For instance less clients,  provide full connection string for 
XA_OPEN().
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
This Problem was first fixed in DB2 V10.5 FixPack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.06.2013
10.03.2014
10.03.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList