Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Team ,
we are facing below issue. But the task is running. and slowly changes are getting captured.
source is saphana
target : Azure sql db
00028240: 2024-04-22T01:28:14 [SOURCE_CAPTURE ]T: RetCode: SQL_ERROR SqlState: S1000 NativeError: 146 Message: [SAP AG][LIBODBCHDB DLL][HDBODBC] General error;146 Resource busy and NOWAIT specified: (lock table failed on vid=3, owner's lockMode: EXCLUSIVE, transID: 24627011275) [1022502] (ar_odbc_stmt.c:2816)
00028240: 2024-04-22T01:28:15 [SOURCE_CAPTURE ]T: Failed (retcode -1) to execute statement: 'LOCK TABLE "XXATT"."attrep_cdc_log" IN EXCLUSIVE MODE NOWAIT' [1022502] (ar_odbc_stmt.c:2810)
could you please let us know what could be done.
Thanks.
Hello @suvbin ,
Thanks for reaching out to Qlik Community!
Would you please check:
1. Are there many tasks using the same source SAP HANA endpoint?
2. Could you please increase the value for transaction consistency SAP HANA source endpoint Advanced tab, let's set it to 3000 (from default 60), a sample:
Hope this helps.
John.
Hello @suvbin ,
Just to add the above comments from @john_wang , The main issue is with while reading attrep_CDC_log file is getting locked by another task. Use log table: When this option is enabled, during the task, Replicate copies the changes from the attrep_cdc_changes table to the attrep_cdc_log table. It could be one of your task is already locked this table while reading and hence it's not allowing this task to capture the changes or can also be that at the server restart, replicate services started before the SAP HANA DB was initialized, hence the error.
Hope this answer find you well.
Regards,
Sachin B
Hi @suvbin
As John mentioned, increase the transaction consistency to stop seeing such warnings. Replicate should be able to insert the records after the previous locks get released.
Thanks
Naren
Thank you for the resolutions. customer is trying to implement logstream task. Before it was individual tasks . Need to check if it resolved the issue