UPDATE statements creating null values in target

[MoeE]

Hi support,

Happy new year, I hope all is well for you guys. I have recently come across this issue with a client where there is some odd behaviour. 

The setup is a logstream task from Oracle to Eventhubs in the dev environment. The odd behaviour is whenever a an update occurs on this one specific table in the task, consequently the updated columns + the primary key column become null on the target. It only happens for this one specific table and none of the others in the task.

I discovered in the logs this message. I also checked the Oracle limitations and found that Function-based indexes are not supported. 

Screenshot within Oracle.

This lead me to assume that this strange behaviour is caused as Function-based index is enabled for the table. I will confirm whether this is the only table that has function-based index enabled. I just need someone to to confirm whether this is indeed the cause of this strange behaviour. In the meantime, I will also try to test it in my environment.

Any help with this is greatly appreciated.

Regards,

Mohammed

[MoeE]

Hi Sushil,

I've looked at the redo log and it seems that all columns are there. Do you have any insight on the mechanics behind how exactly transformations occur in a CDC task? Specifically in the case where you're adding an extra column? The issue behaviour occurs simply even if we add the column and insert some text as the value, it doesn't need to be grabbing data from the source. Any thoughts? 

Regards,

Mohammed