Recently, in a quick Golden Gate testing setup, there was a situation where export/import of data for replication was partial just for prototyping.
In Golden Gate replication, online redo/archive logs are extracted and full SQL statements are formed.
Now, when you have a partial import and export of the data, and run some simulation tests with real application load, you might get to a situation, where application is deleting data but the tables are not included in the export/import (or in the prototype database).
Golden Gate happily runs a cleanup process to synchronize all tables via delete statements the application has done, even if the tables do not exist. For this reason, the performance will degrade in the catchup phase on an active system.
In partial export/imports, Golden Gate can also be configured to skip any delete operations for certain tables or you can disregard certain tables in the replication.
For this situation, there’s a Golden Gate configuration parameter.
GETDELETES | IGNOREDELETES
Valid for Extract and Replicat
Use the GETDELETES and IGNOREDELETES parameters to control whether or not Oracle
GoldenGate processes delete operations. These parameters are table-specific. One
parameter remains in effect for all subsequent TABLE or MAP statements, until the other
parameter is encountered.
Syntax GETDELETES | IGNOREDELETES
You can also skip tables:
Valid for Extract
Use the TABLEEXCLUDE parameter with the TABLE and SEQUENCE parameters to explicitly
exclude tables and sequences from a wildcard specification. TABLEEXCLUDE must precede all
TABLE and SEQUENCE statements that contain the objects that you want to exclude.
Syntax TABLEEXCLUDE <exclude specification> [NORENAME]
Example In the following example, the TABLE statement retrieves all tables except for the table