|
Problem IT07942
|
Status: Closed |
WHEN (SPECIAL)REGISTERS ARE SET IN CLI, PROTOCOL IS VIOLATED FOR XA TRANSACTION IN FEDERATION ENVIRONMENT. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
DB2 federation fails with sql0998 error due to violation of
protocol for distributed transaction processing.
When special registers are set by users for connection in
federation setup, SQL statements fails with -998 error due to
invalid transaction state.
The error happens due to violation of distributed transaction
processing protocol in db2 where the special register settings
erroneoulsy marks the beginning of DUOW when in fact
the first explicit SQL after the connection establishment should
mark the beginning of DUOW. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 and Fix Pack 7 *
**************************************************************** |
| Local Fix: |
To avoid the issue not to have special register for federated
setup.
For example: if the issue is caused by CurrentFunctionPath
parameter, remove CurrentFunctionPath from CLI cfg and
amend the app so that it calls all catalogued routines
explicitly i.e. "CALL CLS.sp_foo" rather than "CALL sp_foo". |
| Solution |
Problem was first fixed in DB2 Version 10.5 and Fix Pack 7 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.03.2015
19.01.2016
27.04.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
