DB2 FOR LUW / DB2FORLUW / A10 - DB2

An XA application might not close client side cursors on XA 
rollback, and this behavior rises SQL0502N at second OPEN 
request. 
This problem is only applicable to withhold cursors, i.e. 
xa_open is set with HOLD_CURSOR=T. 
 
The following code illustrates one of the scenario to cause 
SQL0502N. 
 
1. Open a withhold cursor and make a XA transaction. 
EXEC SQL DECLARE CUR1 CURSOR WITH HOLD FOR <query string> FOR 
UPDATE; 
EXEC SQL OPEN CUR1; 
EXEC SQL FETCH CUR1 INTO :hv1; 
EXEC SQL UPDATE ORG SET <colname>=:hv1 WHERE CURRENT OF CUR1; 
 
2. Rollback the transaction. 
EXEC CICS SYNCPOINT ROLLBACLK; 
 
3. Open the cursor again. 
EXEC SQL OPEN CUR1; 
-> this request fails with SQL0502N. 
 
All cursors will be closed on rollback even if withhold cursors. 
However DB2 might not close client side cursors. This defect 
ensures to close client side cursors after xa_rollback. 
NOTE: Server side cursors are closed in this scenario.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use XA application on DB2 client.                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* An XA application might not close client side cursors on XA  * 
* rollback, and this behavior rises SQL0502N at second OPEN    * 
* request.                                                     * 
* This problem is only applicable to withhold cursors, i.e.    * 
* xa_open is set with HOLD_CURSOR=T.                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to V10.1 FixPack 1 or later.                  * 
****************************************************************

Close all cursors after rollback.

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 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
 

This problem was first fixed in DB2 V10.1 FixPack 1.

not known / see Local fix

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

14.06.2012
30.11.2012
30.11.2012