Filtering DDL Replication
By default, all DDL is passed to Extract.
You can use the filtering with DDL parameter method to filter DDL
operations so that specific (or all) DDL is applied to the target database according
to your requirements. Valid for native DDL capture. This is the preferred method of
filtering and is performed within Oracle GoldenGate, and both Extract and Replicat
can execute filter criteria. Extract can perform filtering, or it can send the
entire DDL to a trail, and then Replicat can perform the filtering. Alternatively,
you can filter in a combination of different locations. The
DDL
parameter gives you control over where the filtering is performed, and it also
offers more filtering options, including the ability to filter collectively based on
the DDL scope (for example, include all MAPPED
scope).
Note:
If a DDL operation fails in the middle of a
TRANSACTION
, it forces a commit, which means that the
transaction spanning the DDL is split into two. The first half is committed
and the second half can be restarted. If a recovery occurs, the second half
of the transaction cannot be filtered since the information contained in the
header of the transaction is no longer there.