Re: Problem with the thick oracle driver ORA-24387: Invalid attach driver



"Guy" <guyharel13@xxxxxxxxx> wrote...

After deciding to use the thick driver instead of the thin,

You probably have your reasons for that, although it reduces the portability
and flexibility of your application significantly.

I suddently had the following exception in one of my Java app,
during the" executeQuery()".

java.sql.SQLException: ORA-24387: Invalid attach driver

Load driver and connect were not excepting. I managed to figure
out that it was because I was linking with "ojdbc14.jar" instead
of "classe12.jar".

So what is "ojdbc14.jar" for ? Is it normal that only the thin
driver work, not the thin, and no compile or link error is produced ?

In my experience the thin driver suffice more than enough, and is less
error-prone than any of the "thick" drivers, as the thin driver is
"self-contained", not relying on other components you have to have installed
on your client machine.

The difference should be that "classes12.jar" is for use with jdk/jre
version 1.2 and 1.3, while "ojdbc14.jar" is for use with later versions of
the jdk/jre (1.4 and 1.5).

However, it becomes even more complicated than that when you're not using
the thin driver. When using the "thick" drivers (e.g. oci), you have to have
a native Oracle client installed on your machine as well, and *that* must
correspond to the version of the DBMS itself.

If you look closer at Oracle's download pages, you'll see that there are
*many* versions of both "classes12.jar" and "ojdbc14.jar", depending on what
version of the Oracle DBMS you're working against.

So my guess is rather that you accidentally used a "ojdbc14.jar" for the
"wrong" version of DBMS, which you resolved by using a "classes12.jar" for
the "right" version of DBMS.

/// Bjorn A



.



Relevant Pages

  • Re: Oracle JDBC error - SOLVED!
    ... " deptName, schoolName, division, dean, AVC, HOD, ... The OCI driver would be, the thin driver would not. ...
    (comp.databases.oracle.server)
  • Re: java study books
    ... Because Oracle wants us to realize that it uses less resources than ... The thin driver does not require the Oracle ...
    (comp.lang.java.programmer)
  • Re: java study books
    ... Because Oracle wants us to realize that it uses less resources than ... The thin driver does not require the Oracle ...
    (comp.lang.java.programmer)
  • Re: java study books
    ... Because Oracle wants us to realize that it uses less resources than ... The thin driver does not require the Oracle client ... removing the extra driver means that the JDBC layer uses less resources. ...
    (comp.lang.java.databases)
  • Re: Java vs SQL Server float datatype limits
    ... table ischecked for data purity it will of course produce errors. ... double into a float column. ... corresponds correctly to the DBMS column. ... So I would have imagined that an SQL Server driver either handle the ...
    (microsoft.public.sqlserver.jdbcdriver)