DB2 FOR LUW / DB2FORLUW / 970 - DB2

When the JDBC/JCC driver switches between XA (2 phase commit) 
local/global transactions in some cases it may not reuse an 
existing TransportObject.  Instead it creates a new connection 
which results in a connection leakage and you may notice that 
increasing JDBC property maxTransportObject may delay the amount 
of time before the application hangs. 
 
Another possible symptom is XAER_OUTSIDE (Resource Manager doing 
work outside global transaction) or hang when trying to start a 
new XA transaction. 
 
This error applies only when the JDBC/JCC driver is connected to 
DB2 for z/OS using the XA connection.

See ERROR DESCRIPTION.

Set JDBC/JCC property: 
 
queryCloseImplicit=DB2BaseDataSource.QUERY_CLOSE_IMPLICIT_NO (2) 
 
Please note this workaround only resolves the XAER_OUTSIDE 
issue.  It does not resolve the hang or connection leakage 
problem.

DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Fix was first included in v9.7 Fixpack 2 (s100514).  At minimum 
this fix should be applied to the client.

See LOCAL FIX.

forerunner  : APAR is sysrouted TO one or more of the following: IC67695 IC67698 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

09.04.2010
19.07.2010
19.07.2010

9.7.FP2