DB2 FOR LUW / DB2FORLUW / B10 - DB2

The "UOW log space used" value can grow to impossible high 
values when the application is running in an XA environment. 
 
This is because the counter value will not get reset when doing 
the XPREPARE, and the counter will just increase. 
 
e.g. the following java code will cause the counter to increase, 
although there is a commit that should reset the counter to 0. 
 
public class Main { 
 
    public static void main(String[] args) { 
        try{ 
            DB2XADataSource db2XADataSource = new 
DB2XADataSource(); 
            db2XADataSource.setDatabaseName(args[0]); 
            db2XADataSource.setUser(args[1]); 
            db2XADataSource.setPassword(args[2]); 
 
            XAConnection xaConnection = 
db2XADataSource.getXAConnection(); 
            XAResource xaResource = 
xaConnection.getXAResource(); 
            Xid xid2 = new MyXid(new byte[]{0x20}, new 
byte[]{0x22}); 
            for(int i=0;i<1000000;i++) { 
                xaResource.start(xid2, XAResource.TMNOFLAGS); 
                String sql = "insert into test select * from 
syscat.tables fetch first 10 rows only"; 
 
xaConnection.getConnection().createStatement().execute(sql); 
                xaResource.end(xid2, XAResource.TMSUCCESS); 
                xaResource.prepare(xid2); 
                xaResource.commit(xid2, false); 
                System.out.println("Iteration"+i); 
            } 
 
        } 
        catch (Exception e) 
        { 
            System.out.print(e.getMessage()); 
        } 
    } 
}

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher               * 
****************************************************************

Using MON_GET_UNIT_OF_WORK to retrieve the log space used 
information.

DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
 

First fixed in DB2 11.1 Mod 2 Fix Pack 2

not known / see Local fix

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

01.11.2016
23.06.2017
23.06.2017