Alternatives to Oracle JDBC thin driver?
rubz
Given the amount of messages about the bugginess of Oracle's JDBC
thin driver, I'm pretty reticent to use it (I'll test it and report
back here...)
But in the meantime can anyone recommend a more stable driver for
Oracle (preferably one that doesn't cost thousands...)
Cheers
Rubz
This message sent via http://www.talkway.com/. Surf Usenet!
Jeff McFarlane
Considering the cost-effectiveness of Oracle's JDBC Thin Driver (free!),
I wouldn't say the comments here are related at all to bugginess. It's
more related to misuse, and lack of support for the driver. There are
alot of questions, and not alot of answers. That doesn't = buggy. That
= lack of knowledge. Oracle's JDBC Thin Driver seems very effective, as
long as you use it right. The biggest problem seems to be in
deployment, not in development.
Phil Bradley
Jeff
I agree about your comments on Oracle's JDBC type 4 (thin) driver. We have
30 people who use it heavily every day in a very complex environment and we
never get problems. **It is not buggy**. We found one fairly archane bug
related to isolation level (although very important to us). There are two
issues with it as far as I am concerned.
1. It is not supported! And when Oracle means not supported it means
**not** supported. I have had a reasonably heavy hitter in Oracle trying to
pursue the above bug. He is essentially being ignored.
2. There are questions about it being thread safe. My most recent
information indicates it is (for most purposes) thread safe. Any further
information on thread safety of the type 4 driver would be appreciated.
Phil Bradley
David Griffiths
I'm sorry, I disagree.
We've been using it heavily for 5 months on two large development project
(100,000 users on one, and 40,000 on the other) and have found several
critical bugs.
Oracle has an open bug, #610012, that relates to a connection. Your
connection will frequently raise an SQL Exception when creating or preparing
a statement. The exact text is "No more data to read from socket". I don't
know how you could have missed that, unless you a recreating your connection
all the time. We have a work-around, but many of our users will be running
over low-speed modems. A dropped connection can add several seconds to a
query. We are already worried about performance; this does not ease our
minds.
We have also found that queries will hang if selecting a single column with
exactly 254 bytes in it. This problem disappeared when we moved to the beta
drivers we got from our local Oracle rep. But we aren't sure if we want to
put beta drivers into production.
We aren't using the drivers wrong, and their general functionality is
excellent. But we want working drivers. Oracle has not made a real effort to
update these drivers. They have not changed since December.
By the way, we are using the 7.3.4 drivers against a 7.3.x database, not the
Oracle 8 drivers against an Oracle 8 DB. If you are using a different
version of the drivers and DB, the you may infact not see any of these bugs.
David Griffiths
GTE Enterprise Solutions.
bob pasker
you won't find Type 4 drivers from anyone except
Oracle because in order to implement SQL*NET you need to
use Oracle proprietary technology, which they have
not shown to be interested in licensing. the same
goes for Sybase and TDS.
--bob pasker
r...@weblogic.com
Toby Mckenzie
Hi,
Has anyone else experienced problems with the isClosed() method on the
connection class. I have a pool of connections, over night these connections
appear to become 'stale'. But when I call isClosed() it returns false. Is there
any other way of determining the status of the connection.
Any help appreciated