| Author |
upgrade to database causes memory fault when running app
|
Marilyn de Queiroz
Sheriff
Joined: Jul 22, 2000
Posts: 9033
|
|
We were using COM.ibm.db2.jdbc.app.DB2Driver (a type-2 driver). It was working fine with this driver until an upgrade to the database (to DB2 v8). But now it's causing a memory fault when using the original driver.
So we switched to com.ibm.db2.jcc.DB2Driver (using as a type-2 driver) which does not cause the memory fault.
The app copies from a table in one database and writes to an identical table in a different database.
I tried (with the old driver) increasing the JVM memory from 128 to 384m. I also tried decreasing the batch write size from 400 to 100. Neither change resolved the problem. Only using the new driver resolved the issue.
Does anyone have any ideas about could be happening here?
|
JavaBeginnersFaq
"Yesterday is history, tomorrow is a mystery, and today is a gift; that's why they call it the present." Eleanor Roosevelt
|
 |
Jeanne Boyarsky
internet detective
Marshal
Joined: May 26, 2003
Posts: 26192
|
|
Marilyn,
I'm confused. The pre-db2 8 driver from IBM isn't working with db2 8? Or am I reading the question wrong.
If this is it, I wouldn't be surprised. You often have to upgrade drivers when a new version of the database comes out. Especially for vendor supplied drivers.
|
[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
|
|
Marilyn de Queiroz
Sheriff
Joined: Jul 22, 2000
Posts: 9033
|
|
|
Well, it's a different driver. In theory they are both supposed to work with DB2 v8. In actuality, the old driver works with most apps and not with some apps and the new driver works with most apps (including the ones driver #1 doesn't) and not with some other apps (that driver #1 works with). Very frustrating.
|
|
 |
|
|
subject: upgrade to database causes memory fault when running app
|
|
|
0
