Is anyone using the 9.2.0.1 or 9.2.0.3 Oracle drivers (JDK 1.4 version: ojdbc14.jar)?

If so, does it operate correctly??

Anything to watch out for?

I'm getting as far as my logon page, when the Session.find (on the username and password) doesn't return the row (even though the data *does* exist in the database). Note that this *does* work with the DataDirect Oracle driver against the same database and configuration.. Any suggestions? I can't see anything in the FAQ, manual, or previous forum entries.

Correction: the 9.2.0.1 version *does* run correctly against the database, which is 9.2.0.2. The 9.2.0.3 JDBC driver still does not seem to work, which is probably not surprising (given that its a later version than the database itself)

I'm just getting into Hibernate, so I can't comment on it's use of the Oracle driver, but I am using 9.2.0.3 thin driver with another application, and it has been working okay. I use it against databases with varying versions of 9i, from 9.0.1.3.0 to 9.2.0.4.0.


Maury...

We are using Hibernate since version 1.2.1 (currently dev on 2.1b4) with Oracle 9.2.0.1 on both Windows & Linux, together with JDK1.4 and ojdbc14.jar.

Works perfectly so far - no particular issue discovered...

I discovered an issue that might explain the 9.2.0.3 driver not working from within Hibernate (or any other tool, for that matter): the table I was referencing had char(40) columns rather than the intended varchar2(40), and the sql statement I was issuing was saying something like this..



Because char(40) is padded out to 40 characters wide (varchar2 isn't), the SQL statement above should actually return NO results.. so I changed the table definition to use varchar2(40) instead of incorrect char(40), and the 9.2.0.3 driver worked first time. Interestingly, the DataDirect driver worked with both char(40) and varchar2 (40).. which it probably should *not* have done.