DB2 - Problem description
Problem IT17755 | Status: Closed |
"UOW LOG SPACE USED" IN APP SNAPSHOT NEVER RESET WHEN USING XA TRANSACTION | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
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 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to the latest fixpack of DB2 V10.1, V10.5 or V11.1. * **************************************************************** | |
Local Fix: | |
Using MON_GET_UNIT_OF_WORK to retrieve the log space used information. | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT17717 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 01.11.2016 01.03.2017 01.03.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |