WILDCARDRESOLVE
Valid For
Extract and Replicat
Description
Use the WILDCARDRESOLVE
parameter to alter the rules for processing wildcarded table specifications in a TABLE
, SEQUENCE
, or MAP
statement. WILDCARDRESOLVE
must precede the associated TABLE
, SEQUENCE
, or MAP
statements in the parameter file.
The target objects must already exist in the target database when wildcard resolution is attempted. If a target object does not exist, Replicat abends.
Default
DYNAMIC
Syntax
WILDCARDRESOLVE {DYNAMIC | IMMEDIATE}
-
DYNAMIC
-
Source objects that satisfy the wildcard definition are resolved each time the wildcard rule is satisfied. The newly resolved object is included in the Oracle GoldenGate configuration upon resolution. This is the default. This is the required setting for Teradata.
Do not use this option when
SOURCEISTABLE
orGENLOADFILES
is specified.WILDCARDRESOLVE
will always be implicitly set toIMMEDIATE
for these parameters.DYNAMIC
must be used when using wildcards to replicate Oracle sequences with theSEQUENCE
parameter.To keep the default of
DYNAMIC
, an explicitWILDCARDRESOLVE
parameter is optional, but its presence helps make it clear to someone who is reviewing the parameter file which method is being used. -
IMMEDIATE
-
Source objects that satisfy the wildcard definition are processed at startup. This option is not supported for Teradata. This is the forced default for
SOURCEISTABLE
.This option does not support the Oracle interval partitioning feature. Dynamic resolution is required so that new partitions are found by Oracle GoldenGate.
Example
The following example resolves wildcards at startup.
WILDCARDRESOLVE IMMEDIATE TABLE hq.acct_*;