Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
vzhang
Contributor
Contributor

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

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 

Labels (2)
3 Replies
kalpesh97
Contributor II
Contributor II

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

lyka
Support
Support

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
Contributor II
Contributor II

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)