Hello forum members,
My query is on soft delete operations.
For certain tables, when my source operation is: delete then, target should set one of flag column to : Y(sayings its deleted) instead deleting it physicall from target.
For this i tried to ues: UPDATEDELETES parameter.
Its working as expected but when same record(which is deleted before) is inserted at source, replicat throwing error saying: record already exists. So key violation issue.
If i use HANDLECOLLISIONS its working without error, but its not best practices to use HANDLECOLLISIONS parameter in production because of few downsides of it rite.
So, how we normally tackle this requirement in Goldenagate. Any otherways, please let me know
--
Regards,
KK.