|
Problem IC96685
|
Status: Closed |
RETURN ERROR WHEN MULTI-TRANSPORT TM ATTEMPTS TO XACOMMIT/XAROLLBACK WHEN THERE IS WITH-HOLD CURSOR IN USE. |
| product: |
DB2 CONNECT / DB2CONNCT / A10 - DB2 |
| Problem description: |
Currently DB2 does not support cursors defined with option to
maintain resources across multiple units of work - 'WITH HOLD'
attribute, when using TM with multi-transport port model like
Tuxedo. The DB2 however returns OK without any action if
xacommit/xarollback is actually attempted by such TM and
with-hold cursor is in use.
This APAR is to change the behaviour to return XAER_RMERR back
to TM on xacommit/xarollback instead of OK, so the incorrect
configuration can be caught earlier. In addition to that the DB2
will log message into db2diag.log informing about unsupported
configuration. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.1 FP4 or newer fix pack *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem First Fixed in DB2 Version 10.1 Fix Pack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.10.2013
17.07.2014
17.07.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
