This content has been marked as final. Show 4 replies
Did you find anything? we had the same problem. We are using 9i thin driver connect to 8.1.7 oracle db server on NT 4.0. We got all kinds of errors, SDU mismatch, invalid package length.
The recommendation from Oracle is to move to JDBC/thin 188.8.131.52.
We haven't tried that yet and we haven't found any other solutions either.
I've got the same problem so i downloaded JDBC 184.108.40.206 But I've got error message again..
so i checked all Oracle drivers in my CLASSPATH and i saw 8i drivers there!!! I found then in /project-path/WEB-INF/lib/ dir in Tomcat (I running it under JBuilder 9) I think that's JBuilders problem 'cause after each compile they have to delete ALL files from lib dir and then place current project libs only!
I'm experiencing the same problem using Oracle 220.127.116.11, jdk1.4. I was seeing the same kinds of errors (Size Data Unit (SDU) mismatch, Protocol violation, Bad packet type, Unexpected packet) using classes12.jar. After a) reading this post and b) realizing that I was using the wrong driver (classes12.jar is only for jdk1.2 and 1.3), I upgraded to driver 18.104.22.168 (ojdbc14.jar).
After adding the new driver (I'm using the thin driver), my application is still stalling in the same place - when trying to read a clob (either at clob.length() or clob.getCharacterStream()). The only difference is that now, no exception is thrown.
I feel like I'm close - but what should have fixed it, is not. There is nothing in the CLASSPATH or anything like that pointing to the old driver. The fact that it used to throw an exception and now does not tells me that the new driver is being used.