These steps add the processes necessary to send data from the secondary system to the primary database.

Perform these steps on the secondary system.

1. Use the ADD EXTRACT command to create a primary Extract group. For documentation purposes, this group is called extn.

   ADD EXTRACT extn, {TRANLOG | INTEGRATED TRANLOG}, BEGIN time

2. Use the ADD EXTTRAIL command to add a local trail. For documentation purposes, this trail is called en.

   ADD EXTTRAIL en, EXTRACT extn

   For Extract, specify the extn group to write to this trail.

3. Use the EDIT PARAMS command to create a parameter file for the extn group. Include the following parameters plus any others that apply to your database environment. For possible additional required parameters, see the Oracle GoldenGate installation and setup guide for your database.

   -- Identify the Extract group:
   EXTRACT extn
   -- Specify database login information as needed for the database:
   [SOURCEDB dsnn][, USERIDALIAS alias]
   -- Specify the local trail that this Extract writes to
   -- and the encryption algorithm:
   ENCRYPTTRAIL algorithm
   EXTTRAIL en 
   -- Exclude Replicat transactions. Uncomment ONE of the following:
   -- Db2 z/OS, Db2 LUW, Db2 IBM i, and Oracle:
   -- TRANLOGOPTIONS EXCLUDEUSER Replicat_user
   -- Oracle integrated capture:
   -- EXCLUDETAG tag
   -- SQL Server:
   -- TRANLOGOPTIONS EXCLUDETRANS FILTERTABLE schema.checkpointtable
   -- Oracle:
   -- TRACETABLE trace_table_name
   -- Log all scheduling columns for CDR and if using integrated Replicat
   LOGALLSUPCOLS
   -- Specify tables to be captured and (optional) columns to fetch:
   TABLE [container.|catalog.]owner.* [, FETCHCOLS cols | FETCHCOLSEXCEPT cols];

   Note:

   To replicate Oracle DBFS data, specify the internally generated local read-write DBFS tables in the TABLE statement on each node. For more information on identifying these tables and configuring DBFS for propagation by Oracle GoldenGate, see Applying the Required Patch in Using Oracle GoldenGate for Oracle Database.

Perform these steps on the secondary system.

1. Use the ADD EXTRACT command to create a data pump group. For documentation purposes, this group is called pumpn.

   ADD EXTRACT pumpn, EXTTRAILSOURCE en, BEGIN time

   For EXTTRAILSOURCE, specify en as the data source.

2. Use the ADD RMTTRAIL command to add a remote trail that will be created on the primary system. For documentation purposes, this trail is called rt.

   ADD RMTTRAIL rt, EXTRACT pumpn

   For EXTRACT, specify the pumpn data pump to write to this trail.

3. Use the EDIT PARAMS command to create a parameter file for the pump_2 group. Include the following parameters plus any others that apply to your database environment.

   -- Identify the data pump group:
   EXTRACT pumpn
   -- Specify database login information as needed for the database:
   [SOURCEDB dsnn][, USERIDALIAS alias]
   -- Decrypt the data only if the data pump must process it.
   -- DECRYPTTRAIL
   -- Specify the name or IP address of the primary system
   -- and optional encryption of data over TCP/IP:
   RMTHOSTOPTIONS system_1, MGRPORT port_number, ENCRYPT encryption_options
   -- Specify the remote trail and encryption algorithm on the primary system:
   ENCRYPTTRAIL algorithm
   RMTTRAIL rt 
   -- Specify tables to be captured:
   TABLE [container.|catalog.]owner.*;

   Note:

   To replicate Oracle DBFS data, specify the internally generated local read-write DBFS tables in the TABLE statement on each node. For more information on identifying these tables and configuring DBFS for propagation by Oracle GoldenGate, see Configuring the DBFS File System in Using Oracle GoldenGate for Oracle Database.

Perform these steps on the primary system.

1. Create the Replicat checkpoint table after using the DBLOGIN command to connect to the database. See ADD CHECKPOINTTABLE in Command Line Interface Reference for Oracle GoldenGate.

2. Run the command:

   ADD CHECKPOINTTABLE schema.checkpointtable

3. Use the ADD REPLICAT command to create a Replicat group. For documentation purposes, this group is called reps.

   ADD REPLICAT reps
   [, PARALLEL | INTEGRATED | COORDINATED [MAXTHREADS number]]
   , EXTTRAIL rt, CHECKPOINTTABLE schema.checkpointtable

   For EXTTRAIL, specify remote_trail_1 as the trail that this Replicat reads.

4. Use the EDIT PARAMS command to create a parameter file for the rep_2 group. Include the following parameters plus any others that apply to your database environment.

   -- Identify the Replicat group:
   REPLICAT reps
   -- Specify database login information as needed for the database:
   [TARGETDB dsns][, USERIDALIAS alias]
   -- Specify error handling rules:
   REPERROR (error, response)
   -- Specify tables for delivery, threads if coordinated Replicat 
   -- and conflict-resolution:
   MAP [container.|catalog.]owner.*, TARGET owner.*, COMPARECOLS (ON operation {ALL | KEY | KEYINCLUDING (col_list) | ALLEXCLUDING (col_list)}), RESOLVECONFLICT (conflict type (resolution_name, resolution_type COLS (col[,...]))
   [, THREAD (thread_ID)]
   [, THREADRANGE (thread_range[, column_list])]
   ;
   -- Specify mapping of exceptions to exceptions table:
   MAP [container.|catalog.]owner.*, TARGET owner.exceptions, EXCEPTIONSONLY;
   

   Note:

   To replicate Oracle DBFS data, specify the internally generated local read-write DBFS tables in the TABLE statement on each node.