Semantic model refresh error

[jgao]

Hi team,

My Semantic model got refreshed hourly by a Azure Databricks workflow.
The data source is Databricks as well.

The refresh works normally most of the time except a same error happens every 2 or 3 days.
The error is showing:

Data source error: Retry attempts for failures while executing the refresh exceeded the retry limit set on the request.
0xC112001C: DataSource.Error: ODBC: ERROR [08000] [Microsoft][Hardy] (35) Error from server: error code: '0' error message: 'GetCrossReference finished with operation state: INITIALIZED_STATE'.. DataSourceKind = Databricks. DataSourcePath = {"host":"azuredatabricks.net","httpPath":"\/sql\/1.0\/warehouses\/"}. OdbcErrors = #table({"SQLState", "NativeError", "Message"}, {}). . The exception was raised by the IDbCommand interface.
0xC112001C: The command has been canceled.. The exception was raised by the IDbCommand interface.
0xC11C0006: The current operation was cancelled because another operation in the transaction failed.
0xC112001C: The command has been canceled.. The exception was raised by the IDbCommand interface.
0xC112001C: The command has been canceled.. The exception was raised by the IDbCommand interface.
0xC112001C: The command has been canceled.. The exception was raised by the IDbCommand interface.
0xC112001C: The command has been canceled.. The exception was raised by the IDbCommand interface.
0xC112001C: The command has been canceled.. The exception was raised by the IDbCommand interface.

May I ask for some help?
Thanks!

[Anonymous · Accepted solution]

Hi @jgao ,

Please try below steps:

1. Review Databricks Cluster Logs: Since the error mentions GetCrossReference finished with operation state: INITIALIZED_STATE, it's crucial to review the logs of your Databricks cluster around the time the error occurred.

2. Optimize Databricks Queries: The error could be a result of timeouts or resource constraints. Optimizing your Databricks queries to be more efficient might help. Consider reviewing your queries for any potential optimizations, such as filtering unnecessary data early in the query or using more efficient join types.

3. Adjust Retry Settings and Timeout: If the issue persists, consider adjusting the retry settings and timeout for the refresh operation.

Best regards,
Community Support Team_Binbin Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.