Fixes are available
DB2 Version 9.5 Fix Pack 3b for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 5 for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 2a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 6 for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 7a for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 4a for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
APAR status
Closed as program error.
Error description
This issue affect the DB2 Universal (JCC) JDBC driver. If a routine is called within an XA unit of work, and that routine performs a commit on return, that commit is outside the XA transaction but the result is that the unit of work is closed on the server side. Once an xa end is flowed to end the unit of work, an XAER_NOTA (not a valid transaction) message will be flowed back to the requestor. In future, we will flow RDBCMTOK=False (RDB Commit OK = false) at the start of the conversation, which will cause us to ignore the commit reply returned by the server outside of the transaction.
Local fix
Do not code stored procedures to commit on return.
Problem summary
ERROR DESCRIPTION: This issue affect the DB2 Universal (JCC) JDBC driver. If a routine is called within an XA unit of work, and that routine performs a commit on return, that commit is outside the XA transaction but the result is that the unit of work is closed on the server side. Once an xa end is flowed to end the unit of work, an XAER_NOTA (not a valid transaction) message will be flowed back to the requestor. In future, we will flow RDBCMTOK=False (RDB Commit OK = false) at the start of the conversation, which will cause us to ignore the commit reply returned by the server outside of the transaction.
Problem conclusion
Fixed in DB2 version 8 Fixpak 16.
Temporary fix
Comments
APAR Information
APAR number
IZ07301
Reported component name
DB2 CUE SOLARIS
Reported component ID
5724B6202
Reported release
820
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-10-25
Closed date
2009-02-25
Last modified date
2009-02-25
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 CUE SOLARIS
Fixed component ID
5724B6202
Applicable component levels
R820 PSY
UP
R910 PSY
UP
R950 PSY
UP
R810 PSN
UP
Document Information
Modified date:
25 February 2009