6.20 CATALOGEXCLUDE

Valid For

Extract, Replicat, DEFGEN

Description

Use the CATALOGEXCLUDE parameter to explicitly exclude source objects in the specified container or catalog from the Oracle GoldenGate configuration when the container or catalog name is being specified with a wildcard in TABLE or MAP statements. This parameter is valid when the database is an Oracle container databasef, where fully qualified three-part names are being used.

The positioning of CATALOGEXCLUDE in relation to parameters that specify files or trails determines its effect. Parameters that specify trails or files are: EXTFILE, RMTFILE, EXTTRAIL, RMTTRAIL. The parameter works as follows:

  • When a CATALOGEXCLUDE specification is placed before any TABLE or SEQUENCE parameters, and also before the parameters that specify trails or files, it applies globally to all trails or files, and to all TABLE and SEQUENCE parameters.

  • When a CATALOGEXCLUDE specification is placed after a parameter that specifies a trail or file, it is effective only for that trail or file and only for the TABLE or SEQUENCE parameters that are associated with it. Multiple trail or file specifications can be made in a parameter file, each followed by a set of TABLE, SEQUENCE, and CATALOGEXCLUDE specifications.

CATALOGEXCLUDE is evaluated before evaluating the associated TABLE or SEQUENCE parameter. Thus, the order in which they appear does not make a difference.

See also the EXCLUDEWILDCARDOBJECTSONLY parameter.

Default

None

Syntax

CATALOGEXCLUDE {container}
container

The source Oracle container that is to be excluded. A wildcard can be used. Follow the rules for using wildcards described in Administering Oracle GoldenGate.

Examples

Example 1   

This example omits the pdb1 pluggable database.

EXTRACT capt
USERIDALIAS alias1
RMTHOST sysb, MGRPORT 7809
RMTTRAIL /ggs/dirdat/aa
CATALOGEXCLUDE pdb1
TABLE *.*.*;