We are listening to an Oracle db (18 and above) for 77 tables in CDC with Qlik Replicate (2022.11.0.208). We have activated Supplemental Logging on DB source, but for 7 of the 77 tables we have unexpected behavior. In fact, when we register UPDATEs on these, the message we get from the source is incomplete. Only the fields that are updated in the transaction are non-NULL, while all others are just NULL. Is there any other configuration (besides Supplemental Logging) to check source side? We have UPDATE on all tables, why is the problem only on these 7?
I agree with Dana that you need to add supplemental logging on all the columns. Additionally, enable store changes to validate the same data in the _ct table to determine if the null values coming from the source or not.
Also, try to create a test task with one problematic table and add verbose logging on source capture and check how the data is replicating.
first of all thanks a lot for the suggestions.
@Dana_Baldwin when you talk about "filter or transformation on the table", are you referring to the ones I added on the task ? Because there is almost always the same filter for all 77 tables (see photo) but as I said only for 7 I have the NULL problem. The field is always part of the PRIMARY KEY, could it be sufficient to activate the supplemental logging for the PRIMARY KEY first? Or is it needed for all columns?
@narendersarva Do I have the possibility to print the message value directly in the task log?
There may be other conditions/factors for these 7 tables, please check https://help.qlik.com/en-US/replicate/November2022/Content/Global_Common/Content/SharedReplicateHDD/...