|
Problem IC92966
|
Status: Closed |
XA_END may RETURN XA_RBOTHER instead of XAER_RMFAIL after reporting communication error. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
DB2 client returns XA_RBOTHER after communication failure ( eg
after hitting -30081) with DB2 server if dynamic registration (
eg using MQ as TM) is in use and communication error is hit
on the first SQL of global transaction.
Here is an example error SQL30081:
Linux x86_64
SQL30081N A communication error has been detected.
Communication protocol being used: "TCP/IP". Communication API
being used: "SOCKETS". Location where the error was detected:
"192.168.123.161". Communication function detecting the error:
"send". Protocol specific error code(s): "110", "*", "*".
SQLSTATE=08001 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB version 10.1 fixpack 3. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 UDB Version 10.1 FixPack 3. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC95389
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.06.2013
04.11.2013
04.11.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
