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:
http://download.oracle.com/docs/cd/E15881_01/doc.104/gg_syb_inst_v104.pdf



Leave a Reply 1

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


rsv1999

rsv1999

Answer is D;

The type of key that is being used by GoldenGate depends on the definition of a given table and whether there are any overrides
by means of a KEYCOLS clause. GoldenGate will use a primary key, if available, or a unique key/index (selection is dependent
on the database). In the absence of those definitions, all columns of the table are used, but a KEYCOLS clause overrides all existing key types. For columns that are being used by GoldenGate as a key, the characters in the names must be valid for inclusion
in a WHERE clause. This list is all-inclusive; a given database platform may or may not support all listed characters