Skip to main content
Announcements
Accelerate Your Success: Fuel your data and AI journey with the right services, delivered by our experts. Learn More
cancel
Showing results for 
Search instead for 
Did you mean: 
guilherme-matte
Partner - Creator
Partner - Creator

Failed to start bulk apply transaction

Hello Team!

I'm having issues with one task in Replicate when using and Oracle Endpoint to Azure SQL DB

The task runs fine, but at 4AM when an internal job runs on the server, I start having the following issue:

 

Failed to start bulk apply transaction
Failed to execute delete statement.
~{FAQAAKW0khrf8AhRPieIDR0GA+Tk9lH+Ly8/YEfx1/JuCV1z9MCD2otGj7Rk3Eu93RbqYADGNWREHoPb8PjStY2rd0uOuLmSv8YmEIwXaqcD+i7an77DocHGp+mGQWfcOO5//rbV8kO6u/56Ooz2nAfO5UzLxv7Fa6UHidjaXzHXzFJhfCVs8KiKMqcVwLQOfBVVk66OcnIxjJwFekFUmWDyMOyDW18BYRx667+c7asLullIsL8w37TAPOxr8NZ00GZCUufDs8O1k3H+M74HWbosxj2QCY2m7n84jdeR6Hkb//vfqpvKU8PiYnJAmNqIPXoMNcZ86RqRuD4Z6p+qq7T1Zz650tEstqEqYHgSH0L7TOghWxqjNDBqe10d1GSzfawqhMrzxNsvDGv6+Y2HoEK8s9cWsbod7R4J4o/gqMW+p+zFYPJbPncXv2xG7J3SGeW7oirml/cDiVEOyI4Rtxu/6WR3m7nuUddL2DMVZLQ0FbEBjXp84xlOFII4TP4vUKyQhw77hLYmm6M365vM6eVmBlnffHJetEohtb0MPPYCW68NCqy6qS2LPGgkFZnd8+Ga+B5HXm4/VemIj74QhRlmQ9Zmzc4bj9ik1BFR1JnzW550}~
RetCode: SQL_ERROR SqlState: HYT00 NativeError: 0 Message: [Microsoft][ODBC Driver 18 for SQL Server]Query timeout expired
Failed (retcode -1) to execute statement: 'DELETE FROM [FINPROD].[BIF3_ITEM_CODE_DETAILS] FROM [attrep_changesC50A62A66CFF4128] WHERE ([FINPROD].[BIF3_ITEM_CODE_DETAILS].[ITEM_CODE]= CAST ( [attrep_changesC50A62A66CFF4128].[seg1] as varchar(80)) COLLATE SQL_Latin1_General_CP1_CI_AS OR ([FINPROD].[BIF3_ITEM_CODE_DETAILS].[ITEM_CODE] IS NULL AND [attrep_changesC50A62A66CFF4128].[seg1] IS NULL)) AND [attrep_changesC50A62A66CFF4128].[seq] >= ? AND [attrep_changesC50A62A66CFF4128].[seq] <= ?'

 

From here, the task starts writing to the target super slowly, barely noticeable. Which ends up needing a manual stop since the CDC starts pilling up changes.  The log repeats the error and warnings until the task stops.

 

guilhermematte_0-1690932076940.png

The tables here only have Unique Index, so no PK are generated on the target (only Unique Indexes)

Any ideas on what could be the source of this issue?

 

Kind Regards!

 

Labels (2)
12 Replies
lyka
Support
Support

Hello,

 

The error is happening on the target. So you should increase the parameter on the target endpoint and not on the source endpoint.

https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-Query-timeout-expired/ta-p/17...

 

Thanks

Lyka

 

MoeyE
Partner - Creator III
Partner - Creator III

Hi everyone,

I'm experiencing the same error and was wondering if a solution was found. It would be great to share.

Thanks,

Mohammed

Heinvandenheuvel
Specialist III
Specialist III

@MoeyE  - Maybe you want to clarify 'the same' - if _exactly_ the same - same error, similar tables, then fine, let's stays here in this post. I would also like the know the final resolution from  @guilherme-matte 

For clarity you may want to start your own post, with your own details, with a link back to this post.

Anyway.... Is there a PK on the target table as required or just a UI? With just a Unique Index on target, and large tables, target execution will be slow and possibly unworkable.

Hope this helps.

Hein.