Configuring the Primary Extract in Classic Capture Mode

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

These steps configure Extract to capture transaction data in classic mode.

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.

   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.
   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.