Topic
4 replies Latest Post - ‏2013-04-17T10:28:45Z by chuck@edmonds
chuck@edmonds
chuck@edmonds
33 Posts
ACCEPTED ANSWER

Pinned topic DB2 V10.1

‏2013-04-16T23:12:38Z |

I have a Java server application that has been running fine on 9.7.  I upgraded to 10.1 and, with the same environment, am getting the following error at application start:

java.lang.UnsatisfiedLinkError: no db2jdbc in java.library.path

 

Anybody know what changed between 9.7 and 10.1 that would be causing this?

 

Thanks

  • nivanov1
    nivanov1
    53 Posts
    ACCEPTED ANSWER

    Re: DB2 V10.1

    ‏2013-04-16T23:56:55Z  in response to chuck@edmonds

    Looks like you're still using the type 2 JDBC driver, which has been deprecated since DB2 8.2 and has been finally discontinued in DB2 10.1.

    You should start using the type 4 (JCC) driver.

    • chuck@edmonds
      chuck@edmonds
      33 Posts
      ACCEPTED ANSWER

      Re: DB2 V10.1

      ‏2013-04-17T01:51:13Z  in response to nivanov1

      The app driver is working fine in 9.7 and it's still present in 10.1.  The docs indicate that for local access the type 2 driver is more efficient than the type 4 driver. 

       

      I'll try changing the driver and see if that does anything, however.  Thanks for the info.

    • chuck@edmonds
      chuck@edmonds
      33 Posts
      ACCEPTED ANSWER

      Re: DB2 V10.1

      ‏2013-04-17T02:53:59Z  in response to nivanov1

      I made the change and got rid of the driver load failure but am now getting the following error message:

      [jcc][10389][12245][3.65.77] Failure in loading native library db2jcct2, java.lang.UnsatisfiedLinkError: no db2jcct2 in java.library.path:  ERRORCODE=-4472, SQLSTATE=null @ ConnectionBuilderThread.run()

       

      I have checked the LD_LIBRARY_PATH and both lib64 and lib32 are on the path.

       

      I'm bummed!!

    • chuck@edmonds
      chuck@edmonds
      33 Posts
      ACCEPTED ANSWER

      Re: DB2 V10.1

      ‏2013-04-17T10:28:45Z  in response to nivanov1

      I got it.  It was a permissions problem.  Thanks for your response.