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

XARESOURCE.START FAILS WITH XAER_INVAL, ERRORCODE=-4228 IF SUPPORT FOR
LOOSELY-ENABLED TRANSACTIONS ENABLED

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
In the WebSphere Application Server 7.0 environment, support for 
XA loosely-coupled transactions has been enabled via the 
following APARs 
WwbSphere Application Server: PM26010 
IBM Data Server Driver for JDBC and SQLJ: PK78198 
 
The WebSphere APAR extends the datasource custom property 
'transactionBranchesLooselyCoupled' to the IBM Data Server 
Driver for JDBC and SQLJ. 
The IBM Data Server for JDBC and SQLJ APAR, introduces an new XA 
flag, TMLCS (8388608) which enables sharing of DB2 locks on XA 
branches 
that have same global transaction ID but different branch 
qualifiers. 
 
Upon setting this property to 'true', however, the application 
failed with the following exception: 
 
[11/11/10 13:01:01:871 CET] 0000001c WSRdbXaResour E 
DSRA0302E: 
XAException occurred.  Error code is: XAER_INVAL (-5). 
Exception is: 
[jcc][t4][10401][12066][4.9.78] XA exception: XAER_INVAL 
ERRORCODE=-4228, SQLSTATE=null 
 
The XA exception XAER_INVAL maps to the error message "Invalid 
arguments". Support for the TMLCS flag was missing from the 
DB2XAResource code. 
This will be corrected in a future release of the driver.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 Fix Pack 6                                * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First Fixed in DB2 9.7 Fix Pack 6
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC73312 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.12.2010
09.05.2017
09.05.2017
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList