ResultSet.TYPE_FORWARD_ONLY and ResultSet.CONCUR_READ_ONLY -JDBC

SailPoint Human Fabric (SHF) SHF Discussion and Questions
,
1

Hey Sailors ,

while doing test connection for one of our JDBC application (which is connecting databricks at backend) we are getting the following error any idea

[ ConnectorException ] [ Error details ] The server encountered an unexpected error while contacting target system during test configuration operation. Please check the logs. Only ResultSet.TYPE_FORWARD_ONLY and ResultSet.CONCUR_READ_ONLY are supported

I suspect this is the issue with jar of databricks

thanks in advance
Avinash

2

FYI we have cloned of our JDBC application which is connection to databricks using VS code but getting the following error

We have detected an error from the managed system. Error Received: Message Status(500) Error response from connector: Policy restrictions prevented decryption of field ‘undefined.password’ for source ‘333333333333333’. Allowed Sources: [1111111111111111111111111]

I have removed and added the creds back but still same error any suggestions on this

4

Hello Sailors ,

while performing test connection we are getting the following error

image
image1094×632 43.3 KB

any idea on this

thanks in advance
Avinash

5

Hi Avinash,

Could you let me know if you’re using any code during the configuring application? Also it would be great if you can help by letting us know the provided queries during application configuration.

As error state by default, a JDBC ResultSet is TYPE_FORWARD_ONLY (meaning the cursor can only move from the beginning to the end) and CONCUR_READ_ONLY (meaning it cannot be updated programmatically).

6

Hi @pkMishra ,

thanks for your reply im not using any sort of code for the application configuration

I was also referring the error code on stack overflow couldn’t figure out the issue

and this is the test connection query for the databricks

SELECT current_date AS connection_test_date,current_user() AS connected_user,current_catalog() AS catalog,current_schema() AS schema;

and this is the referrrence for how to fetch tables from databricks source

7

Ok, I would like to check if the provided queries contains the DB table name as I see in above DB name is missing. Also, I wanted to check if the provided queries is working as expected through DB query dashboard. Can you confirm on above.

8

Hello @amulpuru ,

Are you using the latest version of databricks JDBC driver? Can you try once with 2.7.1 version. I saw somewhere, its working with that version.

9

Hi @pkMishra ,

I above test connection Query connects to Default Catalogue and Default Schema in Databricks and the select Query is also similar

catalog-name.schema-name.table-name

SELECT * FROM testCatalogue.sailpoint_connect.testTable;