Filtering with the DDL Parameter

The DDL parameter is the main Oracle GoldenGate parameter for filtering DDL within the Extract and Replicat processes.

When used without options, the DDL parameter performs no filtering, and it causes all DDL operations to be propagated as follows:

• As an Extract parameter, it captures all supported DDL operations that are generated on all supported database objects and sends them to the trail.

• As a Replicat parameter, it replicates all DDL operations from the Oracle GoldenGate trail and applies them to the target. This is the same as the default behavior without this parameter.

When used with options, the DDL parameter acts as a filtering agent to include or exclude DDL operations based on:

• scope

• object type

• operation type

• object name

• strings in the DDL command syntax or comments, or both

Only one DDL parameter can be used in a parameter file, but you can combine multiple inclusion and exclusion options, along with other options, to filter the DDL to the required level.

• DDL filtering options are valid for a primary Extract that captures from the transaction source.

• When combined, multiple filter option specifications are linked logically as AND statements.

• All filter criteria specified with multiple options must be satisfied for a DDL statement to be replicated.

• When using complex DDL filtering criteria, it is recommended that you test your configuration in a test environment before using it in production.

See DDL parameter syntax and additional usage guidelines in the Reference for Oracle GoldenGate.

Note:

Before you configure DDL support, it might help to review How DDL is Evaluated for Processing.