Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Mar 8, 2023 5:36:51 AM
Mar 8, 2023 5:36:51 AM
Replicating a table from an MS-CDC source endpoint fails with:
E: Fitness check - failed:
When MS-Replication is enabled on the source, it creates an MS-Replication log reader job, which then reads from tlogs and populates the distribution database with the changes.
When you apply MS-CDC at the same time on the source, this creates an MS-CDC capture job, which then also reads from the tlogs, but populates the change tables.
The MS-CDC capture job could not run as the sp_repldone process, which marks the changes out the logs as replicated, could be owned by only one job. The sp_repldone process will in this situation be owned by the MS-Replication log reader job.
To mitigate this, make the following changes for your MS-CDC endpoint:
This tells Qlik Replicate MS-CDC not to check for the MS-CDC capture job as it doesn’t rely on it.
For more information on how to add Internal Parameters, see: Qlik Replicate: How to set Internal Parameters and what are they for?
Qlik Replicate MS-CDC source endpoint
Hello,
I am currently using QCDI, and I am getting a similar error related to FITNESS CHECK FAILED. My demo database is already enabled for CDC.
Do you know where should I do the necessary adjustments to solve this problem?
Thanks!
Hello @rolmontero
We've looked into this for you.
A support ticket is necessary for us to be able to proceed with a proper investigation - please log a ticket with us and we'll assist you.
When logging the ticket, include the link to this article and the screenshot and information you've provided us previously.
All the best,
Sonja
Hi @rolmontero
You can add "Internal Properties" in the QCS data connection - for example:
Please add skipMscdcJobFitnessCheck = true.
Please let me know if this works for you
Thank you
Avidar
Hello @avidary_qlik ,
I resume my QCDI learning, and I just tried your suggestion and an error appeared.
I'll keep trying to make this platform to work!
Hello again,
Does anyone know what is the cause of this error? It didn't appear the last time I move data in the replication task:
Thanks again!
Hi @rolmontero
Thank you for your reply.
As we need more information like logs, JSON file, and project export files.
The best way is to open a support case.
Can you please open a case?
Thank you
Avidar
Hello @avidary_qlik ,
I don't think I will be considered in a support ticket since this is a personal practice. I'm just using an Adventure Works database; it is for intended for a customer or something. I will try anyway, though.
Thanks for your help