UnsatisfiedLinkError

Thread view:

Anurag - 19 Jul 2007 12:17 GMT

Hi,
I am using Oracle 10_2 with java on Websphere. i face following error
messages
at
oracle.jdbc.oci8.OCIDBAccess.RefCursorBytesToDBStatement(OCIDBAccess.java:
2426)

at
oracle.jdbc.driver.OracleStatement.getCursorValue(OracleStatement.java:
3882)

at
oracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:
6104)

at
oracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:
5892)

at
oracle.jdbc.driver.OracleCallableStatement.getObject(OracleCallableStatement.java:
707)

at
com.ibm.ws.rsadapter.jdbc.WSJdbcCallableStatement.getObject(WSJdbcCallableStatement.java:
428)

at com.lxnx.ols.toolkit.dp.DataAttributeStore.getValue
Anyone help me..

Reply to this Message

Roedy Green - 19 Jul 2007 14:24 GMT

see
http://mindprod.com/jgloss/runerrormessages.html#UNSATISFIEDLINKERROR

Signature

Roedy Green Canadian Mind Products
The Java Glossary
http://mindprod.com

Reply to this Message

Bjorn Abelli - 19 Jul 2007 17:09 GMT

"Anurag" <anurag.cs@gmail.com> wrote...

> I am using Oracle 10_2 with java on Websphere. i face following
> error messages
> at
> oracle.jdbc.oci8.OCIDBAccess.RefCursorBytesToDBStatement(OCIDBAccess.java:
> 2426)

[snipped rest of error messages]

The first thing that comes to mind is if you're running compatible versions
of the "Oracle driver set"?

As it seems that you don't use the thin driver (why not?), but the
oci-driver, the version of the jdbc-driver must match to the installed
Oracle native client.

If you don't have a Oracle native client installed, well, there's your
answer.

Either install the appropriate one, or use the thin driver instead (my
recommendation).

If you do have a Oracle native client installed, well, the error message
(UnsatisfiedLinkError), suggests that you probably are using the "wrong"
driver for that client. Each version of the native client has a
corresponding jdbc-driver to go with it.

Another probable cause can be in the line of Roedy's answer, that you've got
some paths mixed up.

When you have installed the Oracle client, the installer usually adds the
"correct" paths to both jdbc-driver, the dll, and the client itself, but it
could also happen that you (or Websphere) has overridden those settings
somehow.

But as I suggested above, none of these problems occur if you use the thin
client instead...

/// Bjorn A

Reply to this Message

Bjorn Abelli - 19 Jul 2007 17:12 GMT

"Bjorn Abelli" <bjorn_abelli@DoNotSpam.hotmail.com> wrote...

> "Anurag" <anurag.cs@gmail.com> wrote...
>
[quoted text clipped - 8 lines]
> But as I suggested above, none of these problems occur if you use the thin
> client instead...

I meant to say; "the thin jdbc-driver"...

With that, you don't need to have the Oracle native client installed...

/// Bjorn A

Reply to this Message

UnsatisfiedLinkError

Free Magazines