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



After deciding to use the thick driver instead of the thin, 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 ?

.



Relevant Pages

  • Re: connecting to an oracle database... errors...
    ... > driver did not consult the tnsnames.ora (Oracle Net) config file at all. ... The thin driver was originally intended to be downloaded to ... For Oracle9i the OCI driver is required for performance ...
    (comp.lang.java.databases)
  • Re: Solaris 10 install on Dell 6950, MegaRAID problems
    ... They seem to be keeping this secret. ... The above seems to be part of what I need to do, but thin on detail. ... Are you saying I can just create an iso image from the driver itself? ...
    (comp.unix.solaris)
  • Re: hardware not supported
    ... Sergey Limarenko wrote: ... > why don't supported ethernet card ... bring you a new driver. ... The point of my first comment was that drivers don't appear out of thin ...
    (freebsd-questions)
  • Re: windows error codes
    ... Driver Development Tools: Windows DDK ... This indicates that a kernel-mode program generated an exception which the error handler did not catch. ... For a complete list of exception codes, see the ntstatus.h file located in the inc directory of the Windows DDK. ... This article describes how to troubleshoot a "STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED" error message. ...
    (microsoft.public.windowsxp.general)
  • RE: getting Kmode Exception Not Handled error
    ... The address at which the exception occurred 0xf7163ab0 ... Faulty device driver or system service. ... Disabling memory caching of the BIOS might also resolve the error. ...
    (microsoft.public.win2000.setup)