Your browser does not support JavaScript. This help page requires JavaScript to render correctly.
Previous
Previous
 
Next
Next

Designating an Alternate Key for a Replicated Table

Oracle must be able to uniquely identify and match corresponding rows at different sites during data replication. Typically, Oracle replication uses the primary key of a table to uniquely identify rows in the table. When a table does not have a primary key, you must designate an alternate key. This alternate key can be a column or set of columns that Oracle can use to uniquely identify rows in the table during data replication.

Caution: To ensure that Oracle can identify rows and preserve the integrity of replicated data, applications should not be allowed to update the identity columns of a table.

When you create a new master group that has a table that does not have a primary key, or attempt to add a table that does not have a primary key to a master group, the Create Master Group Wizard automatically displays the Set Alternate Key Columns page so that you can identify an alternate identity column or set of columns for the replicated table.

API Equivalent: DBMS_REPCAT.SET_COLUMNS

Related Topics

Managing Master Groups