SQL to logstream failed with "Buffer might have been truncated due to 'half - word' boundary - thus - retracted back."

[vzhang]

The task is to get tables from AlwaysOn SQL server to logstream. while the task is running fine for a day, the next day we got "Buffer might have been truncated due to 'half - word' boundary - thus - retracted back." error and resuming job won't work due to the position is lower than the saved position. 

Anybody encountered the same or similar errors? Thanks

Qlik Replicate 

Vincent 

[kalpesh97]

We are seeing similar warnings but the task continue to run. Can anyone from Qlik respond?

[lyka]

Hello,

An Assertion message is generated when something happens that is not expected. In general they should be reported to support as sometimes they describe a problem and sometimes they can be treated as informational.

To further troubleshoot, enable source capture and target apply again to verbose and wait for another assertion to occur.

Thanks

Lyka

[kalpesh97]

Hello Lyka,

We can not turn on verbose logging because this is a production system. To clarify, we are not using log stream. Here are few sample messages if that helps. 

[ASSERTION ]W: Buffer might have been truncated due to 'half - word' boundary - thus - retracted back. Variable sized field 'UlddName': Storage pointed offset = '0', previous offset = '391'. Column is PK segment? false (sqlserver_log_formatter.c:1015)

 [ASSERTION ]W: Buffer might have been truncated due to 'half - word' boundary - thus - retracted back. Variable sized field 'CompanyName': Storage pointed offset = '78', previous offset = '132'. Column is PK segment? false (sqlserver_log_formatter.c:1015)

[brunnod]

Hi,

We're getting the same error, did you get a solution for that?

0245691: 2024-11-25T04:46:04 [ASSERTION ]W: Buffer might have been truncated due to 'half - word' boundary - thus - retracted back. Variable sized field 'CardCode': Storage pointed offset = '88', previous offset = '96'. Column is PK segment? true (sqlserver_log_formatter.c:1029)

Thanks
Brunno Dias

[sujankudumula]

Hi @lyka  We are facing the same issue with one of the SQL server replication tasks. The Change Processing shows the transactions picked up but nothing applied to the database. The task is running fine and this warning comes up when reading changes from the source database. This is happening intermittently once or twice a week.

[john_wang]

Hello @sujankudumula ,

In general this warning will not cause data missing. We need additional information to understand the issue completely, please open a support ticket and attach the diagnostic packages. Our support team will be more than happy to assist you.

Regards,

John.