DB2 FOR LUW / DB2FORLUW / A10 - DB2

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

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 10.1 fixpack 3.                   * 
****************************************************************

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
 

Problem was first fixed in DB2 UDB Version 10.1 FixPack 3.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC95389 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

10.06.2013
04.11.2013
04.11.2013