Failed to write to changes table

[MoeyE]

Hi,

Has anyone seen these errors before? The correct permissions to truncate are indeed enabled.

Failed (retcode -1) to execute statement: TRUNCATE TABLE [ctl].[attrep_changesE3A0D63108A3F061]

RetCode: SQL_ERROR  SqlState: 42S02 NativeError: 4701 Message: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Cannot find the object "attrep_changesE3A0D63108A3F061" because it does not exist or you do not have permissions. Line: 1 Column: -1

Failed to truncate table ctl.attrep_changesE3A0D63108A3F061

Failed to truncate net changes table

The table exists on the target. The target is Microsoft SQL Server.

Regards,

Mohammed

[sureshkumar]

Hello @MoeyE 

Could you please review the SQL server logs for that specific timeframe for any locking information?

If you've enabled ""Apply batched changes to multiple tables concurrently" under the batch tuning option, kindly uncheck the option and Resume the task.

Regards,

Suresh

[SachinB]

Hello @MoeyE ,

In general, the attrep_changes table is used as a temporary table to hold operations that are being done against the target tables. This table is only used in CDC.

Please try to stop and resume the task and see if you get the same error, also check is the permission is revoked for this schema ctl

Regards,

Sachin B

[Kent_Feng]

Hi @MoeyE 

According to my experience,  the "Failed to truncate net changes table" error was usually caused by a networking or connection hiccup. As Sachin suggested, stop and resume the task may solve the issue or you can try Suresh' setting tuning which was found to be a solution for one of our support cases.

Regards

Kent 

[MoeyE]

Hi @SachinB , @Kent_Feng ,

Thanks for the answers, much appreciated. Will update to let you know how it goes.

Regards,

Mohammed

[MoeyE]

Hi Suresh,

The "Apply batched changes to multiple tables concurrently" setting is already disabled. I looked through the SQL Server logs at the time of the error and there appears to be a login from the Qlik Replicate user. I'm thinking there was possible a brief disconnection from the target then Replicate reconnected?

Regards,

Mohammed

[sureshkumar]

Hello @MoeyE 

Could be target disconnection.

Regards,

Suresh