Full load table error

[Al_gar]

I have a task setup with Full Load and CDC. One of the tables has a filter condition that tested OK when using the Parse Expression. However, after the full load completed it's showing the table under the "Tables - Error" queue in the Full Load tab , this warning message showed up "Table 'table_name' (subtask 0 thread 1) is suspended. Cannot compute expression, not all column values are in the data record." , and under 'Total Completion' Progress Details shows what it looks a wrong calculation of records:

Nevertheless, the "failed" table is getting CDC updates. What would need to be fixed then to remove the table from the Full Load failed status?

[lyka]

Good Day!

Are you using Oracle as a source endpoint?

Sample Error:

[TASK_MANAGER ]W: Table xxxx (subtask 0 thread 1) is suspended. Cannot compute expression, not all column values are in the data record

"If any Filter/Transformation is applied on particular column, make sure Supplemental logging is enabled for all the columns otherwise the particular table will be suspended"

"When using Oracle as the backend database, any tables you want to capture must be defined with ALL COLUMN SUPPLEMENTAL LOGGING"
-->Please make sure supplementary logging is enabled for the columns in the table 'RESB'

ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS

https://help.qlik.com/en-US/replicate/May2022/Content/Global_Common/Content/SharedReplicateHDD/Oracl...

Please note that you can also add supplemental logging for all fields used in manipulation with ALWAYS and this will also be sufficient, but you must add all fields that you have in manipulation/filters.

Hope this helps!

Thanks

Lyka

[Al_gar]

Hi Lyka,

Using HANA db as source and MS SQL as target.

[lyka]

Hello,

If its a SAP HANA source can you check if deletes or updates are happening on the filtered records?

if yes, then you are hitting this limitation

• Capturing DELETE and UPDATE operations for filtered records is not supported.

https://help.qlik.com/en-US/replicate/May2022/Content/Global_Common/Content/SharedReplicateHDD/SAP-H...

Thanks

Lyka

[Al_gar]

I see there has been an update reported by Replicate for the affected table. Does this mean that the filter limitation could be a hit or miss? Are there any plans to overcome this limitation? or a workaround?