Attunity Replicate Error with SQL Server Source while Change processing

[jigargpatel]

I am trying to set up Attunity Replcate for MS SQL Source and Kafka target. 

Connections are fine and tested. 

I am able to do full load fine. 

However, when i try to process the change , i am getting series of errors.

Task '***' encountered a recoverable error

Task error notification received from subtask 0, thread 0 

Stream component 'st_0_***' terminated
Stream component failed at subtask 0, component st_0_*** 
Error executing source loop

Encountered an unexpeceted error.

Bad Envelope : 

Lsn=00014abc:00003e79:0007,operation=5,TxnId=0000:0491b0c4,Tablename=COMMIT,PageId=,slotId=0,timeStamp=2020-01-29T17:35:53.673,dataLen=0, LCX=99, 

>Invalid data context / LCX Code encountered for TXN operation.

[Ted_Manka · Accepted solution]

Hello Jigarg,

Replicate is trying to validate the type of the events that it gets and in this case the server was not able to validate this event. This doesn't mean that the event is invalid or there is a problem with the event it only means that was not able to validate it. 

a previous example we encountered:resuming the tasks from a timestamp which may fall in the middle of a transaction, so the tasks would read a commit event without a preceding 'start transaction' event and would throw the 'Bad Envelope' error, meaning the task has encountered an invalid transaction context.  

Please set this internal parameter on your SQL Server source endpoint - ignoreTxnCtxValidityCheck  This parameter will allow the task to continue even if was not able to validate the event.

From the Advanced tab of the endpoint, click internal parameters. Type in the parameter name - it will appear in a dialog box beneath. Select that & it will be added to the list of parameters. Click the box to activate it. Click OK to close the parameter window, then click Save on the endpoint.

If that doesn't work please open a support ticket: attunitysupport.qlik.com

Thank you,

Ted Manka

[Rak]

We encountered the same issue while applying some database changes while Qlik tasks were running.

Did adding the ignoreTxnCtxValidityCheck internal parameter resolve the issue?

Also, are there any risks of missing change data or other implications from adding this internal parameter at the source endpoint (Sql Server)?