Member Avatar for Poornima

hi guys,
I'm a new member. By the way, I had an error that showed up on my jdbc program that connected to oracle. It showed 'java.sql.SqlException'. When I looked up on it in a book called Oracle8i Complete Reference, it told me that I could set my environment variables and test run my jdbc connection with a program that was there when Oracle is installed. It was called JdbcCheckup.java. Now its compiling all fine and dandy, but this run time error keeps popping up called java.lang.UnsatisfiedLinkError. Can someone help this fair lady in distress? ;)

E:\Oracle\Ora81\jdbc\demo\samples\oci8\basic-samples>javac JdbcCheckup.java

E:\Oracle\Ora81\jdbc\demo\samples\oci8\basic-samples>java JdbcCheckup
Please enter information to test connection to the database
user: scott
password: tiger
database (a TNSNAME entry):
Connecting to the database...Connecting...
Exception in thread "main" java.lang.UnsatisfiedLinkError: no ocijdbc8 in java.l
ibrary.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1682)
at java.lang.Runtime.loadLibrary0(Runtime.java:822)
at java.lang.System.loadLibrary(System.java:992)
at oracle.jdbc.oci8.OCIDBAccess.logon(OCIDBAccess.java:192)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:142)

at oracle.jdbc.driver.OracleDriver.getConnectionInstance(
va:214)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:193)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at JdbcCheckup.main(JdbcCheckup.java:42)

  • 3 Contributors
  • 2 Replies
  • 199 Views
  • 9 Hours Discussion Span
  • Latest Post Latest Post by Kate Albany

Dani AI

Generated

For : the runtime failure is not a Java-level bug — it means the sample is using Oracle’s OCI-based JDBC and the JVM can’t find the native Oracle client library that the OCI driver requires. Both points already raised by and are correct; below are concrete, safe steps to fix it and a simpler alternative (Thin) that avoids native libraries entirely.

On Windows (quick, actionable):

  • Ensure the Oracle client bin directory is on the OS PATH (or use -Djava.library.path) so the JVM can load the native DLLs. For example, from a command prompt:

    set PATH=C:\path\to\oracle\bin;%PATH%
java -Djava.library.path=C:\path\to\oracle\bin -cp ".;C:\path\to\oracle\jdbc\classes12.zip" JdbcCheckup

  • Confirm the native DLL (the OCI DLL that ships with your client) actually exists in that bin directory and that the JVM and Oracle client are the same bitness (32-bit JVM needs 32-bit client; 64-bit JVM needs 64-bit client).

Prefer the Thin driver unless you need OCI features:

  • The Thin driver is pure Java and removes native-dependency headaches. Replace the OCI URL/driver with a Thin-style JDBC URL and ensure the Oracle JDBC JAR that matches your Java version is on the classpath. Example connection snippet:

    String url = "jdbc:oracle:thin:@hostname:1521:SID";
Connection conn = DriverManager.getConnection(url, "scott", "tiger");

Troubleshooting checklist:

  • Put the correct Oracle JDBC JAR on the application classpath (match jar to your JDK version).
  • Verify PATH / LD_LIBRARY_PATH (or use -Djava.library.path) and restart the shell after changes.
  • Check JVM vs Oracle client bitness.
  • If you don’t need OCI-specific features, switch to the Thin driver to avoid native DLL issues.

These steps expand on ’s classpath note and ’s Thin-driver suggestion with concrete commands and extra checks that commonly solve UnsatisfiedLinkError problems.

Recommended Answers

All 2 Replies

Member Avatar for jwenting

looks like you're missing a jarfile in your classpath. I don't have Oracle installed here so I can't tell you which one, but the name it gives as missing should be a good indication.

Member Avatar for Kate Albany

Poornima,

This sample program is trying to use the OCI (Oracle Call Interface) JDBC driver. This is a platform dependant driver. I would strongly recommend researching how to use the Oracle Thin JDBC driver, unless you have specific need to use the OCI driver. The Thin driver is platform indepentent and is highly optimised, it is as fast and in some cases faster than the OCI driver and will work on any platform without a care in the world.

The reason this sample appplication is not working is because it cannot locate the OCI library. I suspect you will have to set the LD_LIBRARY_PATH enviroment variable to point to the OCI library.

Kate

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.