What errors are likely to occur?

You have implemented multi-master Oracle/Oracle replication without a provision to
exclude transactions committed by a Replicat process. What errors are likely to occur?

You have implemented multi-master Oracle/Oracle replication without a provision to
exclude transactions committed by a Replicat process. What errors are likely to occur?

A.
Inserts will generate a primary key uniqueness violation; deletes will generate a ‘no
matching row’ not found error; updates will continue forever.

B.
None: loop detection is on by default in Oracle.

C.
New inserts will be processed without issue; updates and deletes will generate a “row
not found” error.

D.
Updates and deletes will be replicated without issue new inserts will generate a primary
key uniqueness violation.



Leave a Reply 3

Your email address will not be published. Required fields are marked *


Virginia

Virginia

A.

Options

a) Exclude user
EXCLUDEUSER
http://docs.oracle.com/goldengate/1212/gg-winux/GWURF/gg_parameters174.htm#GWURF712
Typically, this option is used to identify Replicat transactions in a bi-directional or cascading processing configuration, for the purpose of excluding or capturing them

b) Trace Table
ADD TRACETABLE
http://docs.oracle.com/goldengate/1212/gg-winux/GWURF/ggsci_commands077.htm#GWURF291
The trace table prevents Replicat transactions from being extracted again in a bidirectional synchronization configuration

rsv1999

rsv1999

A is correct and not D.

rsv1999

rsv1999

Not B, I meant.