gilta03

Tech Tip: No dbjdbc12 in java.library.path error in Fast Data Masker

Discussion created by gilta03 Champion on Jan 18, 2017

This document can also be viewed at https://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.TEC1482413.html 

 

Issue:

When trying to connect to Fast Data Masker (FDM), I am receiving the following error message: Error: no dbjdbc12 in java.library.path

No dbjdbc12 in java.library.path error.PNG

Steps to reproduce:

  1. Launch FDM.
  2. In the 'Connection Files' pane, click the 'New' button. 
  3. Click on the DBMS drop down list and choose one. 
  4. Enter in all the connection details. 
  5. Click the 'Connect' button. 

    Expected result: I am taken to the FDM masking page. 
    Actual result: I receive the error message "no dbjdbc12 in java.library.path"

 

Environment:
CA Test Data Manager (TDM)- Fast Data Masker (FDM)
Cause:

This issue pertains to having the SQLANYWHERE drivers (sajdbc.jar and sajdbc4.jar) in the FDM lib directory folder. This driver requires an underlying DLL to work, even if you are not connecting to SQLANYWHERE. It will throw an error message no matter what database you are connecting to.

Since TDM release 3.5, certain jar files are no longer shipped with the product. This document describes the jar files that have been removed: https://docops.ca.com/ca-test-data-manager/3-5/en/installing/supported-data-sources 

If you are upgrading to TDM 3.5+ and are seeing this error message, it is because the FDM lib directory folder now contains these jar files and they need to be removed. 

 

Resolution:

There are a few different resolutions to this error message:

#1:

  • Remove the 2 jar files (sajdbc.jar and sajdbc4.jar) from the FDM lib directory folder.
  • The default file path for this folder is C:\Program Files\Grid-Tools\FastDataMasker\lib.
  • After this, close out and re-open FDM since many of these files are loaded upon launch.
  • You should now be able to connect to FDM.

#2

  • If you are using any other database connection other than SQLANYWHERE, like Oracle, you can click the 'OK' button on the error message and ignore it.

#3

  • If you have recently upgraded and have the older version backed up or installed in another location, you can copy and paste the contents (not actual folder) of your old FDM lib folder over to your current FDM lib folder.
  • This way you will have all the jar files you need.
  • All new drivers will remain the same if you only copied the contents of your old folder into the new.
  • After this, close out and re-open FDM since many of these files are loaded upon launch.
  • You should now be able to connect to FDM.

 

Additional Information:

If you face any issues or have any questions about the steps, please open a support case by going to https://support.ca.com/irj/portal/anonymous/newhome  or by calling customer care at http://www3.ca.com/us/support/customer-assistance.aspx.

Outcomes