1.151 SOURCECATALOG
Valid For
Extract and Replicat
Description
Use the SOURCECATALOG
parameter to specify one of the following for subsequent TABLE
or MAP
statements that contain two-part names, where three-part object names are required to fully identify a default source Oracle pluggable database (PDB)
This parameter provides an efficient alternative to specifying the full three-part object name (container.schema.object
or catalog.schema.object
) when specifying source objects from an Oracle consolidated database. Only the two-part name (schema.object
) need be specified in subsequent TABLE
or MAP
statements when SOURCECATALOG
is used. You can use multiple instances of SOURCECATALOG
to specify different default containers or catalogs for different sets of TABLE
statements (or SEQUENCE
statements, if Oracle).
Three-part name specifications encountered after SOURCECATALOG
override the SOURCECATALOG
specification in a TABLE
statement, MAP
statement, or other parameter that takes object names as input.
Default
None
Syntax
SOURCECATALOG {container
}
Example
In the following example, SOURCECATALOG
is used to specify three different source Oracle PDBs in an Extract parameter file.
SOURCECATALOG FINANCE TABLE SAP.*; TABLE REPORTS.*; SOURCECATALOG HR TABLE SIEBEL.*; TABLE REPORTS.*; SOURCECATALOG MFG TABLE CUSTOMER.ORDERS; TABLE REPORTS.*; TABLE HQ.LOCATIONS.*;
In this example, Extract captures the following:
-
All tables in the
SAP
andREPORTS
schemas in theFINANCE
PDB. -
All tables in the
SIEBEL
andREPORTS
schemas in theHR
PDB. -
All tables in the
CUSTOMER
andREPORTS
schemas in theMFG
PDB. -
For the last
TABLE
statement, Extract captures all tables in theLOCATIONS
schema in theHQ
PDB. This statement is a fully qualified three-part name and overrides the previousSOURCECATALOG
specification.
Parent topic: Oracle GoldenGate Parameters