Second System in the Cascade

Configure the Manager process, Replicat group, and data pump on the second system in the cascade.

To Configure the Manager Process on the Second System

On the second system, configure the Manager process.
In the Manager parameter file, use the PURGEOLDEXTRACTS parameter to control the purging of files from the trail.

To Configure the Replicat Group on the Second System

Create a Replicat checkpoint table (unless using Oracle integrated Replicat). See About Checkpoint Table for instructions.
On the second system, use the ADD REPLICAT command to create a Replicat group. For documentation purposes, this group is called rep_1.
```
ADD REPLICAT rep_1 
[, INTEGRATED | COORDINATED [MAXTHREADS number]]
, EXTTRAIL remote_trail_1, 
, BEGIN time
```
Use the EXTTRAIL option to link the rep_1 group to the remote trail remote_trail_1 that is on the local system.

See Parameters and Functions Reference for Oracle GoldenGate for detailed information about these and other options that may be required for your installation.
On the second system, use the EDIT PARAMS command to create a parameter file for the Replicat 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 Replicat group:
REPLICAT rep_1
-- Specify database login information as needed for the database:
[TARGETDB dsn_2][, USERIDALIAS alias]
-- Specify error handling rules:
REPERROR (error, response)
-- Specify tables for delivery and threads if using coordinated Replicat:
MAP [container.|catalog.]owner.table, TARGET owner.table[, DEF template]
[, THREAD (thread_ID)][, THREADRANGE (thread_range[, column_list])]
;
```
Note:

For DB2 for i, you may need to use the ADD TRANDATA command on the target tables if they are not already journaled. Alternatively, you could use the STRJRNPF command to assign the tables to the appropriate journal. If the target tables are not required to be replicated by Oracle GoldenGate, the IMAGES(*AFTER) option can be used with STRJRNPF. Since Oracle GoldenGate operates using transactions, all tables must be journaled to support transactions and this is not the default with DB2 for i.

To Configure an Extract Group on the Second System

On the source, use the ADD EXTRACT command to create an Extract group. For documentation purposes, this group is called ext_2.
```
ADD EXTRACT ext_2, {TRANLOG | INTEGRATED TRANLOG}, BEGIN time [option[, ...]]
```
See Parameters and Functions Reference for Oracle GoldenGate for detailed information about these and other ADD EXTRACT options that may be required for your installation.
On the second system, use the ADD EXTTRAIL command to specify a local trail that will be created on the third system.
```
ADD EXTTRAIL local_trail_2, EXTRACT ext_2
```
Use the EXTRACT argument to link this local trail to the ext_2 Extract group.

On the second system, use the EDIT PARAMS command to create a parameter file for the ext_2 Extract 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 ext_2
-- Specify database login information as needed for the database:
[SOURCEDB dsn_2][, USERIDALIAS alias]
-- Log all scheduling columns if using integrated Replicat
LOGALLSUPCOLS
-- Specify the local trail that this Extract writes to
-- and encryption algorithm:
ENCRYPTTRAIL algorithm
EXTTRAIL local_trail_2
-- Ignore local DML, capture Replicat DML:
IGNOREAPPLOPS
GETREPLICATES
-- Specify tables and sequences to be captured:
SEQUENCE [container.|catalog.]owner.sequence;
TABLE [container.|catalog.]owner.table;

Note:

If replicating DDL operations, IGNOREAPPLOPS, GETREPLICATES functionality is controlled by the DDLOPTIONS parameter.

To Configure the Data Pump on the Second System

On the second system, use the ADD EXTRACT command to create a data pump group. For documentation purposes, this group is called pump_2.
```
ADD EXTRACT pump_2, EXTTRAILSOURCE local_trail_2, BEGIN time
```
Use EXTTRAILSOURCE as the data source option, and specify the name of the local trail.
On the second system, use the ADD RMTTRAIL command to specify a remote trail that will be created on the third system in the cascade.
```
ADD RMTTRAIL remote_trail_2, EXTRACT pump_2
```
Use the EXTRACT argument to link the remote trail to the pump_2 data pump group. The linked data pump writes to this trail.

See Parameters and Functions Reference for Oracle GoldenGate for additional ADD RMTTRAIL options.

On the second system, use the EDIT PARAMS command to create a parameter file for the pump_2 data pump. Include the following parameters plus any others that apply to your database environment.

-- Identify the data pump group:
EXTRACT pump_2
[SOURCEDB dsn_2][, USERIDALIAS alias]
-- Decrypt the data only if the data pump must process it.
-- DECRYPTTRAIL
-- Specify the name or IP address of third system in cascade
-- and optional encryption of data over TCP/IP:
RMTHOSTOPTIONS target_2, MGRPORT port_number, ENCRYPT encryption_options
-- Specify the remote trail and encryption algorithm on the third system:
ENCRYPTTRAIL algorithm
RMTTRAIL remote_trail_2
-- Specify tables and sequences to be captured:
SEQUENCE [container.|catalog.]owner.sequence;
TABLE [container.|catalog.]owner.table;