Limiting Row Changes in Tables That Do Not Have a Key
If a target table does not have a primary key or a unique key, duplicate rows can exist. In this case, Oracle GoldenGate could update or delete too many target rows, causing the source and target data to go out of synchronization without error messages to alert you. To limit the number of rows that are updated, use the DBOPTIONS
parameter with the LIMITROWS
option in the Replicat parameter file. LIMITROWS
can increase the performance of Oracle GoldenGate on the target system because only one row is processed.