Fixes are available
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
Closed as program error.
If the federated two phase commit (F2PC) transaction is from DB2 zOS client, rollback an update transaction can not work for one phase commit (1PC) data source. The DB2 zOS client uses a type 2 client connection as default; the F2PC transaction rollback can work properly against the two phase commit (2PC) data source, but can not work for 1PC data source. For 1PC data source, committing a transaction is used to end a transaction, which causes the rollback problem. Commit or rollback is taken according to the transaction intend to commit or rollback, which can make the F2PC transaction rollback work properly for both 1PC and 2PC data sources. Note: if the data source is defined as a federated two-phase commit data source, even if all updates of a transaction occur on a single data source, then it goes through federated two phase commit processing.? This may have potential performance impact on federation sever.
Turn on two phase phase commit if possible. alter server <server name> options (DB2_TWO_PHASE_COMMIT 'Y')
Users affected: Users of the DB2 for LUW Homogeneous Federation Feature or InfoSphere Federation Server Problem description and summary: See error description.
Problem was first fixed in Version 9.5 FixPak 5 (s091123 ). This fix should be applied on the federation server.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels
22 December 2009