How to configure replication when ON UPDATE CASCADE constraint functionality is enabled on source.
There is no such thing as ON UPDATE CASCADE in Oracle.
Customers generally devise manual means to achieve this on the source database. The means can be a trigger, a PL/SQL code, a deferrable constraint (defer the foreign key check until commit by first updating the parent then child and then commit.) etc.
If the customer is deploying such techniques on source, disable the constraint on target and let the underlying tables replicate the correct value.
In a nutshell,
1. Stop Post
2. Disable referential integrity constraint on target tables that are involved with the ON UPDATE CASCADE
3. Start Post
