Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Want to see what's currently in public preview? We've pulled it all together in one place. Check it out here
cancel
Showing results for 
Search instead for 
Did you mean: 
AgusBudianto
Contributor III
Contributor III

Qlik Replication ODBC SQL_ERROR Connection Failed

Tasks using Simba ODBC connections to Databricks Lakehouse (Delta) Target get error messages, but the tasks still run:

Logs message 1:

RetCode: SQL_ERROR SqlState: 08S01 NativeError: 115 Message: [Simba][Hardy] (115) Connection failed with error: HTTP Response code: 400 , BAD_REQUEST: Invalid SessionHandle: Session [01f08224-d2bc-1feb-b4e2-750c939abc40] is closed.
Failed (retcode -1) to execute statement: REFRESH TABLE `sky_raw_mirror_lfa`.`attrep_changesAD716FF52F3078F7`

Logs message 2:

Allocated 150 ODBC statement handles

1 Solution

Accepted Solutions
DesmondWOO
Support
Support

Hi @AgusBudianto ,

This issue should not be related to ODBC limitations, but my guess is that it could be due to a network issue or idle timeout. Regardless, we need to check the task log to see what happened.

Regards,
Desmond

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!

View solution in original post

3 Replies
DesmondWOO
Support
Support

Hi @AgusBudianto ,

It seems that the connection has expired. Was the Databricks cluster restarted? We need to check your task log for analysis. I recommend creating a support ticket for further assistance.

Regards,
Desmond

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
AgusBudianto
Contributor III
Contributor III
Author

Hi @DesmondWOO 

ok I will try Submit a ticket, but is there any connection limitation using ODBC?

DesmondWOO
Support
Support

Hi @AgusBudianto ,

This issue should not be related to ODBC limitations, but my guess is that it could be due to a network issue or idle timeout. Regardless, we need to check the task log to see what happened.

Regards,
Desmond

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!