# SQLAnywhere DB: No dbjdbc17 in java.library.path **URL:** \ **Category:** SHF Discussion and Questions\ **Created:** [January 27, 2022, 9:36am UTC](https://developer.sailpoint.com/discuss/t/sqlanywhere-db-no-dbjdbc17-in-java-library-path/2816 "2022-01-27T09:36:17Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![Beatriz](https://avatars.discourse-cdn.com/v4/letter/b/f9ae1b/32.png) [@Beatriz](https://developer.sailpoint.com/discuss/u/Beatriz)\ **Post date:** [January 27, 2022, 9:36am UTC](https://developer.sailpoint.com/discuss/t/sqlanywhere-db-no-dbjdbc17-in-java-library-path/2816/1 "2022-01-27T09:36:17Z")
Hello experts, Im trying to integrate a SQL Anywhere db with IdentityNow. When I try to test the connectivity, the conntection works, the problem came when we try to run the accounts aggregation, we obtain: no dbjdbc17 in java.library.path We check that the SQL Anywhere server has defined the path variable to dbjdbc17, but not lucky. Any idea? Than you in advance. Beatriz. ---
**Author:** ![yannick\_beot](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/yannick_beot/32/8985_2.png) [@yannick\_beot](https://developer.sailpoint.com/discuss/u/yannick_beot)\ **Post date:** [January 27, 2022, 11:55am UTC](https://developer.sailpoint.com/discuss/t/sqlanywhere-db-no-dbjdbc17-in-java-library-path/2816/2 "2022-01-27T11:55:30Z")
Hello @Beatriz Did you upload the JDBC driver for SQL Anywhere? At the bottom of the source page, there is a “upload” button to select your jar file and upload it. ---
**Author:** ![Beatriz](https://avatars.discourse-cdn.com/v4/letter/b/f9ae1b/32.png) [@Beatriz](https://developer.sailpoint.com/discuss/u/Beatriz)\ **Post date:** [January 27, 2022, 12:07pm UTC](https://developer.sailpoint.com/discuss/t/sqlanywhere-db-no-dbjdbc17-in-java-library-path/2816/3 "2022-01-27T12:07:14Z")
> [@yannick\_beot](#): > > you upload the JDBC driver for SQL Anywhere? Yes, we already upload the jar and even so, we are still getting the same error when we try to run an aggregation. ---
**Author:** ![yannick\_beot](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/yannick_beot/32/8985_2.png) [@yannick\_beot](https://developer.sailpoint.com/discuss/u/yannick_beot)\ **Post date:** [January 27, 2022, 12:29pm UTC](https://developer.sailpoint.com/discuss/t/sqlanywhere-db-no-dbjdbc17-in-java-library-path/2816/4 "2022-01-27T12:29:47Z")
It seems there is a dependency to a .so file. Did you upload it as well? ---
**Author:** ![Beatriz](https://avatars.discourse-cdn.com/v4/letter/b/f9ae1b/32.png) [@Beatriz](https://developer.sailpoint.com/discuss/u/Beatriz)\ **Post date:** [January 27, 2022, 12:42pm UTC](https://developer.sailpoint.com/discuss/t/sqlanywhere-db-no-dbjdbc17-in-java-library-path/2816/5 "2022-01-27T12:42:52Z")
I tried to upload also the dbjdbc17.dll file but it still not working ☹ ---
**Author:** ![yannick\_beot](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/yannick_beot/32/8985_2.png) [@yannick\_beot](https://developer.sailpoint.com/discuss/u/yannick_beot)\ **Post date:** [January 27, 2022, 6:29pm UTC](https://developer.sailpoint.com/discuss/t/sqlanywhere-db-no-dbjdbc17-in-java-library-path/2816/6 "2022-01-27T18:29:34Z")
I did not manage to make it work with the JDBC driver. However, I manage to make work the JDBC connector with the **jConnect JDBC Driver** (cf. [SAP Help Portal](https://help.sap.com/viewer/98ad9ec940e2465695685d98e308dff5/17.0/en-US/3bd588c76c5f10149824867aa281fadd.html)) My parameters: - URL: `jdbc:sybase:Tds::2638` - Driver: `com.sybase.jdbc4.jdbc.SybDriver` I have only uploaded `jconn4.jar`. A query like `select * from users;` is working for the aggregation. ---
**Author:** ![Beatriz](https://avatars.discourse-cdn.com/v4/letter/b/f9ae1b/32.png) [@Beatriz](https://developer.sailpoint.com/discuss/u/Beatriz)\ **Post date:** [January 27, 2022, 7:03pm UTC](https://developer.sailpoint.com/discuss/t/sqlanywhere-db-no-dbjdbc17-in-java-library-path/2816/7 "2022-01-27T19:03:32Z")
Hello Yannick, First of all, thank you so much for your support. I tried what you said and im getting the error: ![image](https://global.discourse-cdn.com/sailpoint/original/1X/c9058e0df4e0db32c450ea3a35bfc6305fbeaecd.png) I set the same URL structure and the driver as your recommendation. ---
**Author:** ![yannick\_beot](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/yannick_beot/32/8985_2.png) [@yannick\_beot](https://developer.sailpoint.com/discuss/u/yannick_beot)\ **Post date:** [January 28, 2022, 8:53am UTC](https://developer.sailpoint.com/discuss/t/sqlanywhere-db-no-dbjdbc17-in-java-library-path/2816/8 "2022-01-28T08:53:19Z")
Hello @Beatriz Try to upload the `jconn4.jar` or wait a few minutes or restart the CCG service. It probably means that the VA did not receive the driver. It takes a few minutes for the VA to get the file. If you have the proper `jconn4.jar`, the class `com.sybase.jdbc4.jdbc.SybDriver` is present in it. ---
**Author:** ![Beatriz](https://avatars.discourse-cdn.com/v4/letter/b/f9ae1b/32.png) [@Beatriz](https://developer.sailpoint.com/discuss/u/Beatriz)\ **Post date:** [January 28, 2022, 9:42am UTC](https://developer.sailpoint.com/discuss/t/sqlanywhere-db-no-dbjdbc17-in-java-library-path/2816/9 "2022-01-28T09:42:42Z")
Hello @yannick_beot , Yes, you’re right. Now im getting a different error: ![image](https://global.discourse-cdn.com/sailpoint/original/1X/9bb739b06a1eb1d0badc1124aa06ef4cb963408a.png) The database team show me how they are able to login with our user using a SQL management tool, so the user is not block. Any idea? ---
**Author:** ![yannick\_beot](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/yannick_beot/32/8985_2.png) [@yannick\_beot](https://developer.sailpoint.com/discuss/u/yannick_beot)\ **Post date:** [January 28, 2022, 10:24am UTC](https://developer.sailpoint.com/discuss/t/sqlanywhere-db-no-dbjdbc17-in-java-library-path/2816/10 "2022-01-28T10:24:21Z")
Definitively, this seems related to login… It is possible to activate auditing. SAP SQL Anywhere may provide additional information on the login attempts: [https://wiki.scn.sap.com/wiki/display/SQLANY/How+to+Monitor+Connection+Attempts+to+Your+Database+in+SQL+Anywhere](https://wiki.scn.sap.com/wiki/display/SQLANY/How+to+Monitor+Connection+Attempts+to+Your+Database+in+SQL+Anywhere) I see you are using parameters in the connection string. At least, it would ensure that you are targeting the proper host, the proper server and the proper database. You can also try to a simpler password. Mine was not using any special character. I guess that testing the credentials with an administration tool is excluding the case where “user requires a new password to be specified at next login”. ---
**Author:** ![Beatriz](https://avatars.discourse-cdn.com/v4/letter/b/f9ae1b/32.png) [@Beatriz](https://developer.sailpoint.com/discuss/u/Beatriz)\ **Post date:** [January 28, 2022, 12:11pm UTC](https://developer.sailpoint.com/discuss/t/sqlanywhere-db-no-dbjdbc17-in-java-library-path/2816/11 "2022-01-28T12:11:25Z")
Hello @yannick_beot , The problem is that they dont see any info on the trace, is like the tenant is not capable of reach the DB. About the password, its a simple one, it doesnt contain any special character. The JDBC URL is correct, DB team confirm it. ---
**Author:** ![yannick\_beot](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/yannick_beot/32/8985_2.png) [@yannick\_beot](https://developer.sailpoint.com/discuss/u/yannick_beot)\ **Post date:** [January 28, 2022, 1:12pm UTC](https://developer.sailpoint.com/discuss/t/sqlanywhere-db-no-dbjdbc17-in-java-library-path/2816/12 "2022-01-28T13:12:47Z")
Can you look into the CCG logs? Looking at [java - sybase jdbc connection issue - Stack Overflow](https://stackoverflow.com/questions/16444534/sybase-jdbc-connection-issue), it seems that the SQLException is masking exceptions that could give us hints. This SO post and this [one](https://community.oracle.com/tech/apps-infra/discussion/698380/getting-java-sql-sqlexception-jz00l-login-failed-when-connect-to-sybase) are referencing charset issues for instance. Also, can you ensure that the port 2648 is opened from the VA (with a telnet command) for instance. If you do not see anything in the DB logs, it might be a network issue. Again, the analysis of the full stacktrace may help eventually. ---
**Author:** ![yannick\_beot](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/yannick_beot/32/8985_2.png) [@yannick\_beot](https://developer.sailpoint.com/discuss/u/yannick_beot)\ **Post date:** [February 1, 2022, 12:45pm UTC](https://developer.sailpoint.com/discuss/t/sqlanywhere-db-no-dbjdbc17-in-java-library-path/2816/13 "2022-02-01T12:45:03Z")
Hello @Beatriz Did you have time to check all of the proposed test? ---
**Author:** ![Beatriz](https://avatars.discourse-cdn.com/v4/letter/b/f9ae1b/32.png) [@Beatriz](https://developer.sailpoint.com/discuss/u/Beatriz)\ **Post date:** [February 1, 2022, 1:17pm UTC](https://developer.sailpoint.com/discuss/t/sqlanywhere-db-no-dbjdbc17-in-java-library-path/2816/14 "2022-02-01T13:17:38Z")
Hello @yannick_beot, Sorry for the delay. I did the check and I can confirm that the VA is able to stablish the connection via telnet command. So I guess there is not a network related issue. Do you have any documentation about the compatibility between IDN and SQL anywhere. Thank you in advance, Beatriz. ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [July 19, 2023, 2:22pm UTC](https://developer.sailpoint.com/discuss/t/sqlanywhere-db-no-dbjdbc17-in-java-library-path/2816/15 "2023-07-19T14:22:31Z")