Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content
Announcements
UPGRADE ADVISORY for Qlik Replicate 2024.5: Read More
cancel
Showing results for 
Search instead for 
Did you mean: 
_riccardo
Partner - Contributor
Partner - Contributor

Suspended Tables (Databricks Target) due to "Transactional apply" Errors in "Batch optimized" Task

Hi everyone,

I have a task in Qlik Replicate with target Databricks Lakehouse (Delta). Recently, many tables have been suspended due to the following errors:

  • "Performing 'update' operations in "Transactional apply" mode is not supported by Databricks Delta"
  • "Performing 'insert' operations in "Transactional apply" mode is not supported by Databricks Delta"
  • "Performing 'delete' operations in "Transactional apply" mode is not supported by Databricks Delta"

The problem is that the task has always been set to "Batch optimized apply". Does anyone know why this is happening?

Thank you in advance for any insights!

Labels (2)
1 Solution

Accepted Solutions
john_wang
Support
Support

Hello @_riccardo ,

Thanks for the update.

I'd recommend opening a support ticket with the following information:

  1. Set TARGET_APPLY to Verbose and reproduce the issue.

  2. Download the Task Diagnostics Package and attach it to the support ticket.

  3. Decrypt the verbose task log files, compress them, and include them in the ticket as well.

Please note that our support team may request additional information during their investigation.

Regards,

John.

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
john_wang
Support
Support

Hello @_riccardo ,

Please check the article:  transactions apply mode is not supported.

Hope this helps.

John.

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

Hello @john_wang,

Thanks for the suggestion! However, I've already verified that all the tables in this replication task have defined primary keys.

Any other thoughts on why this might be happening?

john_wang
Support
Support

Hello @_riccardo ,

Thanks for the update.

I'd recommend opening a support ticket with the following information:

  1. Set TARGET_APPLY to Verbose and reproduce the issue.

  2. Download the Task Diagnostics Package and attach it to the support ticket.

  3. Decrypt the verbose task log files, compress them, and include them in the ticket as well.

Please note that our support team may request additional information during their investigation.

Regards,

John.

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