We've been using the COM.ibm.db2.jdbc.app.DB2Driver (driver name = IBM DB2 alias). That driver provides both a JDBC 1.2 and a JDBC 2.0-based implementation.
Over the weekend, they upgraded the database to version 8. Some of our java code failed to run and threw OutOfMemoryErrors, so we switched to using the newer driver com.ibm.db2.jcc.DB2Driver (driver name = IBM DB2 Universal Type 2). It provides JDBC 2.0 and most JDBC 3.0 functionality.
The java code now works again. However, we are experiencing weird things with some of our sql... some of the insert statements appear to run correctly (no errors), but there is no data in the tables.
Anyone have any ideas on what could possibly be causing this? [ November 14, 2007: Message edited by: Marilyn de Queiroz ]
JavaBeginnersFaq "Yesterday is history, tomorrow is a mystery, and today is a gift; that's why they call it the present." Eleanor Roosevelt
Perhaps the new DB2 installation does not commit automatically. What is the return value of "connection.getAutoCommit()"? My guess it's false; if so you can use "connection.setAutoCommit(true)" to turn it on again.