Forums Register Login

DB2 upgrade creates jdbc driver problem

+Pie Number of slices to send: Send
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 ]
+Pie Number of slices to send: Send
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.
Can't .... do .... plaid .... So I did this tiny ad instead:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com


reply
reply
This thread has been viewed 1151 times.
Similar Threads
ResultSet is getting closed..
jdbc access to DB2
java.sql.SQLException: No suitable driver
DB2 access from browser using JDBC
WSAD db2 driver failure.
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 29, 2024 04:32:35.