How will the Replicat proceed to identify matching target rows to update or delete?

Neither your source, nor your target table has a primary key, and you have not designated
KEYCOLS. How will the Replicat proceed to identify matching target rows to update or delete?

Neither your source, nor your target table has a primary key, and you have not designated
KEYCOLS. How will the Replicat proceed to identify matching target rows to update or delete?

A.
The first unique key alpha-numerically, excluding virtual columns and nullable columns, will be
treated as the primary key.

B.
This configuration is not supported by GoldenGate; Replicat will abend on updates or deletes.

C.
The first column, excluding virtual columns and nullable columns, will be treated as the pr key.

D.
The combination of all fields up to the first thirty-two will be treated as a compound primary key

Explanation:
Reference:
http://download.oracle.com/docs/cd/E15881_01/doc.104/gg_syb_inst_v104.pdf



Leave a Reply 0

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