Google Big Query scan failing in Purview

Question

I am scanning a google big query project from Purview and getting this error - Error 3805 : Connector Exception - Connection to the database with the URL ( jdbc:bigquery://https://www.googleapis.com/bigquery (followed by project and service accout details) failed :Simba:bigqueryjdbcdriver(100004) Httptransport IO Error:EXEC_JOB_TIMEOUT_ERROR)

The jdbc driver is installed in Self hosted integration runtime and service account is set up in google big query . Can you help please?

Answer 1

@KumKum Rekhari - Thanks for the question and using MS Q&A platform.

It seems like there is an issue with the connection to the Google BigQuery project. The error message indicates that there is a timeout error while executing the job. This could be due to a number of reasons such as network connectivity issues, incorrect credentials, or an issue with the configuration of the scan.

To troubleshoot this issue, I would suggest the following steps:

Check the network connectivity between the self-hosted integration runtime and the Google BigQuery project. Ensure that there are no firewall rules blocking the connection.

Verify that the credentials used to connect to the Google BigQuery project are correct. Ensure that the service account has the necessary permissions to access the project.

Check the configuration of the scan. Ensure that the correct integration runtime is selected and that the credentials are configured correctly.

Check the logs for any additional error messages that may provide more information about the issue.

If you have already checked these steps and are still experiencing issues, please provide me with more information about your setup and the steps you have taken so far.

Answer 2

@PRADEEPCHEEKATLA

we tried updating the firewal rules and ensured the connectivity is there to the Google bigquery from the integration runtime. we know the bigquery credentials are correct and were able to use it to connect from power bi.

not sure what else is missing. what additional logs can we look at to understood the root cause of the error?

Thanks