Reference for Oracle GoldenGate

Valid For

Extract, Data Pump, Distribution Server, and Replicat. Oracle only.

Description

These parameters work in conjunction with the TABLE and TABLEEXCLUDE parameters. Only when a table is included, the partition rules are evaluated.

For consistency, these parameters behave much like their TABLE and TABLEEXCLUDE counterparts.

Wildcarding will be allowed in all name portions.
GLOBALS parameter EXCLUDEWILDCARDOBJECTSONLY is supported
Container portion is only valid in CDB environment.
SOURCECATALOG parameter will take affect when catalog portion is not specified.
Container portion must be specified when SOURCECATALOG is not specified.
If container portion is specified, then it takes precedence over SOURCECATALOG.

If the [container.]schema.table portion of any PARTITION or PARTITIONEXCLUDE rule matches the table, only then additional partition filtering will be performed.

Partition filtering rules are evaluated in the following order:

If the partition name does not match any PARTITION parameter, it is excluded.
If included by the PARTITION parameter, then exclusion rules are evaluated unless it was included by a non-wildcard inclusion rule and EXCLUDEWILDCARDOBJECTSONLY was specified.

Note:

An error occurs if a PARTITION or PARTITIONEXCLUDE parameter has an invalid number of parts.

Syntax

PARTITION [container.]schema.table.partition;
PARTITIONEXCLUDE [container.]schema.table.partition;

For non-CDB, 3 parts must be specified (schema.table.partition). For CDB, either 4 parts must be specified (pdb.schema.table.partition) or 3 parts with a preceding SOURCECATALOG parameter.

Examples

In the following example, partition is excluded because the table is not referenced by any TABLE parameter.

DML on schema.tab2.part

TABLE schema.tab1;
PARTITION schema.tab2.part;

In the following example, partition is included because no partition rule has a table portion matching schema.tab1. Therefore, no partition rule is evaluated.

DML on schema.tab1.part

TABLE schema.tab1;
PARTITION schema.tab2.part;

In the following example, partition is included because both table and partition rules include it.

DML on schema.tab1.part

TABLE schema.tab1;
PARTITION schema.tab*.part;

In the following example, partition is excluded because is only for part1 of schema.tab1:

DML on schema.tab1.part2

TABLE schema.tab1;
PARTITION schema.tab*.part1;

In the following example, partition is excluded because of explicit partition exclude rule.

DML on schema.tab1.part1

TABLE schema.tab1
PARTITION schema.tab*.part1;
PARTITIONEXCLUDE schema.tab1.part*;

This example shows how multiple partition rules can be specified. Partition will be included because it is matched by one of the partition inclusion rules.

DML on schema.tab1.part1

TABLE schema.tab1;
PARTITION schema.tab1.part2;
PARTITION schema.tab1.part1;