TDM: Snowflake does not identify tables after data model scan is complete
search cancel

TDM: Snowflake does not identify tables after data model scan is complete

book

Article ID: 276824

calendar_today

Updated On:

Products

CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

Checking Snowflake connectivity and TDM portal’s ability to model and mask the data. However, the models are not having any elements scanned. The logs contain details of the errors at JDBC level. 

Environment

TDM Portal 4.10.237

Cause

Known Snowflake JDBC Driver limitation.

Resolution

Analyzed the issue from the logs shared from the TDM Portal. It looks like this might be a known Snowflake JDBC Driver limitation or configuration limitation where each query in Snowflake is given a default timeout duration and once its reached Snowflake engine terminates the connection - which is what we see in the logs.

Recommending 2 things to do.

1. If you can increase the default internal timeout parameter for each query in Snowflake it should help (https://docs.snowflake.com/en/user-guide/jdbc-parameters.html#querytimeout)
2. Please raise a ticket with Snowflake and their inputs from Snowflake support on how to fix this issue as it's coming from Snowflake side.

Here are some relevant articles found:
1. Snowflake JDBC throws error while fetching large data : JDBC driver internal error: Timeout waiting for the download of #chunk0
2. net.snowflake.client.jdbc.SnowflakeChunkDownloader : Timeout waiting for the download of #chunk0 - Stack Overflow