Troubleshooting third party drivers
Consider the following troubleshooting tips when you use third party drivers such as JDBC from vendors such as CData, Simba, or DataDirect:
Scanner or profiling jobs fail due to third party driver limitations
Third party driver limitations can be the reason why the scanner job logs to not provide failure details or why metadata is missing in job results.
The following scenarios might occur:
- - The JDBC driver requires a license file. The file is missing from the driver location.
- - Elastic Load Balancing (ELB) that you use on Amazon AWS returns a timeout error after a few minutes and terminates the connection.
- - The driver does not return all metadata or some profiling is failing.
In such cases, before you contact Informatica Global Customer Support, perform the following actions:
- 1. Verify if the JDBC driver allows parameters for activating additional logging in the connection string.
- 2. Analyze the debug log of the driver to determine the root cause of your error.
- Databricks Delta JDBC driver error example
- jdbc:spark://localhost:11000;LogLevel=6;LogPath=/tmp/JDBC_logs
- In this example, use the external query tools to verify if the JDBC connectivity works and if you can see the metadata and data properly.
- CData JDBC driver error example
- jdbc:cdata:d365sales:AuthScheme=AzureServicePrincipal;AzureTenant=<tenant>;OAuthClientId=<client>;OAuthClientSecret=<secret>;OrganizationUrl=<org URI>;Verbosity=5;logfile=/tmp/JDBC_logs/cdata_jdbc.log
- In this example, use the external query tools to verify if the JDBC connectivity works and if you can see the metadata and data properly.