The purpose of this article is help you to set workaround for disabling triggers on target database on Windows platforms with Oracle database 184.108.40.206 and above. On Unix based platforms workaround is not not needed to apply, because dbvisit replicate manage it internally.
Documentation: https://dbvisit.atlassian.net/wiki/display/ugd8/Triggers; https://blogs.oracle.com/UPGRADE/entry/new_11_2_0_4;
//If you want to use bi-directional replication on Windows with triggers
// Disabled triggers can use also people without two way replication.
// From ticket how to rename it:
- installed the new patch
- reverted trigger changes
dbvrep.exe -> replicate.exeand edited the scripts
- started all replication processes.
In next releases we plan to make workaround permanent
Key words: bi-directional replication; Windows; dbvisit replicate; Oracle 220.127.116.11; Oracle 12c; triggers; APPLY_SET_TRIGGER_FIRE_ONCE