Can one avoid a loop when remote tables are updating each other via triggers?
Triggers can easily cause replication errors and even infinite loops in a replicated environment. This happens as the trigger fire more than once on the same data. For example, consider a trigger that inserts a row into a table. When this row is replicated to a remote database(s), the trigger will fire again on the same data, and re-insert a duplicate row into the table. This problem can be solved by using the DBMS_REPUTIL.FROM_REMOTE function.
