Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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
>Invalid data context / LCX Code encountered for TXN operation.
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
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