7 Configuring Capture in Classic Mode

You must adhere to the guidelines in this topic before configuring an Extract in classic mode.

These instructions show you how to configure a basic Extract parameter (configuration) file for the primary Extract, which captures transaction data from the data source, and for a data-pump Extract, which propagates captured data that is stored locally in a trail from the source system to the target system.

You can set up a classic Extract process for intial loading of source data and replicating it.

1. In GGSCI on the source system, create the Extract parameter file.

   EDIT PARAMS name
   

   Where: name is the name of the primary Extract.

2. Enter the Extract parameters in the order shown, starting a new line for each parameter statement. See Table 7-* for more information and parameter descriptions.

   Basic parameters for the primary Extract in classic capture mode

   EXTRACT finance
   USERIDALIAS tiger1 
   LOGALLSUPCOLS
   ENCRYPTTRAIL AES192
   EXTTRAIL /ggs/dirdat/lt
   SEQUENCE hr.employees_seq;
   TABLE hr.*;
   

   Parameter	Description
   EXTRACT group	group is the name of the Extract group. For more information, see Reference for Oracle GoldenGate.
   USERIDALIAS alias	Specifies the alias of the database login credential of the user that is assigned to Extract. This credential must exist in the Oracle GoldenGate credential store, see Establishing Oracle GoldenGate Credentials.
   LOGALLSUPCOLS	Writes all supplementally logged columns to the trail, including those required for conflict detection and resolution and the scheduling columns required to support integrated Replicat. (Scheduling columns are primary key, unique index, and foreign key columns.) You configure the database to log these columns with GGSCI commands. See Configuring Logging Properties.
   UPDATERECORDFORMAT COMPACT	Combines the before and after images of an UPDATE operation into a single record in the trail. This parameter is valid for Oracle Databases version 12c and later to support Replicat in integrated mode. Although not a required parameter, UPDATERECORDFORMAT COMPACT is a best practice and significantly improves Replicat performance. See Reference for Oracle GoldenGate for more information.
   ENCRYPTTRAIL algorithm	Encrypts the local trail. For more information about Oracle GoldenGate trail encryption options, see Administering Oracle GoldenGate.
   EXTTRAIL pathname	Specifies the path name of the local trail to which the primary Extract writes captured data. For more information, see Reference for Oracle GoldenGate
   {TABLE | SEQUENCE} schema.object;	Specifies the database object for which to capture data. TABLE specifies a table or a wildcarded set of tables. SEQUENCE specifies a sequence or a wildcarded set of sequences. schema is the schema name or a wildcarded set of schemas. object is the table or sequence name, or a wildcarded set of those objects. See Administering Oracle GoldenGate for information about how to specify object names with and without wildcards. Terminate the parameter statement with a semi-colon. To exclude tables from a wildcard specification, use the TABLEEXCLUDE parameter. See Reference for Oracle GoldenGate for more information about usage and syntax. For more information and for additional TABLE options that control data filtering, mapping, and manipulation, see Reference for Oracle GoldenGate.

3. Enter any optional Extract parameters that are recommended for your configuration. You can edit this file at any point before starting processing by using the EDIT PARAMS command in GGSCI. For more information, see the Reference for Oracle GoldenGate.
4. Save and close the file.

These steps configure the data pump that reads the local trail and sends the data across the network to a remote trail. The data pump is optional, but recommended.

1. In GGSCI on the source system, create the data-pump parameter file.

   EDIT PARAMS name
   

   Where: name is the name of the data pump Extract.

2. Enter the data-pump parameters in the order shown, starting a new line for each parameter statement. Your input variables will be different. See Table 7-* for descriptions.

   Basic parameters for the data-pump Extract group using two-part object names:

   EXTRACT extpump
   USERIDALIAS tiger1
   RMTHOST fin1, MGRPORT 7809 ENCRYPT AES192, KEYNAME securekey2
   RMTTRAIL /ggs/dirdat/rt
   SEQUENCE hr.employees_seq;
   TABLE hr.*;
   

   Basic parameters for the data-pump Extract group using three-part object names (including a pluggable database):

   EXTRACT extpump
   USERIDALIAS tiger1
   RMTHOST fin1, MGRPORT 7809 ENCRYPT AES192, KEYNAME securekey2
   RMTTRAIL /ggs/dirdat/rt
   TABLE test.ogg.tab1;
   SOURCECATALOG pdb1
   SEQUENCE hr.employees_seq;
   TABLE hr.*;
   SOURCECATALOG pdb2
   TABLE sales.*;
   TABLE acct.*;
   

   Parameter	Description
   EXTRACT group	group is the name of the data pump Extract. For more information, see Reference for Oracle GoldenGate.
   USERIDALIAS alias	Specifies the alias of the database login credential of the user that is assigned to Extract. This credential must exist in the Oracle GoldenGate credential store, see Establishing Oracle GoldenGate Credentials.
   RMTHOST hostname, MGRPORT portnumber, [, ENCRYPT algorithm KEYNAME keyname]	RMTHOST specifies the name or IP address of the target system. MGRPORT specifies the port number where Manager is running on the target. ENCRYPT specifies optional encryption of data across TCP/IP. For additional options and encryption details, see Reference for Oracle GoldenGate.
   RMTTRAIL pathname	Specifies the path name of the remote trail. For more information, see Reference for Oracle GoldenGate.
   SOURCECATALOG container	Use this parameter when the source database is a multitenant container database. Specifies the name of a pluggable database that is to be used as the default container for all subsequent TABLE and SEQUENCE parameters that contain two-part names. This parameter enables you to use two-part object names (schema.object) rather than three-part names (container.schema.object). It remains in effect until another SOURCECATALOG parameter is encountered or a full three-part TABLE or SEQUENCE specification is encountered. Use this parameter when the source database is a multitenant container database. See Reference for Oracle GoldenGate for more information about SOURCECATALOG.
   {TABLE | SEQUENCE} [container.]schema.object;	Specifies a table or sequence, or multiple objects specified with a wildcard. In most cases, this listing will be the same as that in the primary Extract parameter file. TABLE specifies a table or a wildcarded set of tables. SEQUENCE specifies a sequence or a wildcarded set of sequences. container is the name of the root container or pluggable database that contains the table or sequence, if this source database is a multitenant container database. See the SOURCECATALOG description in this table. schema is the schema name or a wildcarded set of schemas. object is the name of a table or sequence, or a wildcarded set of those objects. See Administering Oracle GoldenGate for information about how to specify object names with and without wildcards. Terminate this parameter statement with a semi-colon. To exclude tables or sequences from a wildcard specification, use the TABLEEXCLUDE or SEQUENCEEXCLUDE parameter after the TABLE statement. For more information and for additional TABLE options that control data filtering, mapping, and manipulation, see Reference for Oracle GoldenGate.

3. Enter any optional Extract parameters that are recommended for your configuration. You can edit this file at any point before starting processing by using the EDIT PARAMS command in GGSCI. For more information, see the Reference for Oracle GoldenGate and Optional Parameters for Integrated Modes for additional configuration considerations..
4. Save and close the file.

A parameter file is a plain text file that is read by an associated Oracle GoldenGate process to control the product functionality.