DB2 - Problem description
Problem IT17184 | Status: Closed |
IN XA/PURESCALE ENVIRONMENT, XA-END COULD BE BROADCASTED TO ALL NODES EVEN IF THEY WEREN'T PART OF THE TRANSACTION. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
In XA/Purescale environment, XA-END could be broadcasted to all nodes even if they weren't part of the transaction. When running multiple XA-transactions under the same connection to the database, if one transaction does some remote processing because of 1. DDL 2. implicit rebind/recreate/regenration of package/procedure when invoking a package/function/procedure. the remote nodes visited in this transaction could be used for all subsequent transactions under the same connection. This sends multiple unnecessary XA-END interrupts to remote nodes. During this issue reproduction, we can see the following db2trc points sqljs_ddm_syncctl | sqljsSyncEnd | | sqlrr_xend | | | sqlrxend | | | | sqlrkend | | | | | sqlrr2pd | | | | | | sqlkdInterrupt | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * XA user on pureScale * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 FixPack 9 or later * **************************************************************** | |
Local Fix: | |
Solution | |
Fixed in DB2 Version 10.5 FixPack 9 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.09.2016 27.09.2017 27.09.2017 |
Problem solved at the following versions (IBM BugInfos) | |
9.0. | |
Problem solved according to the fixlist(s) of the following version(s) |