Adding Another Data Pump to an Active Configuration

This procedure adds a data-pump Extract group to an active primary Extract group on the source system. It makes these changes:

The primary Extract will write to a local trail.
The data pump will write to a new remote trail after the data in the old trail is applied to the target.
The old Replicat group will be replaced by a new one.

Steps are performed on the source and target systems.

On the source system, run GGSCI.
Add a local trail, using the name of the primary Extract group for group.
```
ADD EXTTRAIL trail, EXTRACT group
```
For example:
```
ADD EXTTRAIL dirdat\lt, EXTRACT primary
```
Open the parameter file of the primary Extract group, and replace the RMTTRAIL parameter with an EXTTRAIL parameter that points to the local trail that you created.
Caution:

Do not use the VIEW PARAMS or EDIT PARAMS command to view or edit an existing parameter file that is in a character set other than that of the local operating system (such as one where the CHARSET option was used to specify a different character set). View the parameter file from outside GGSCI if this is the case; otherwise, the contents may become corrupted..

Example EXTTRAIL parameter:
```
EXTTRAIL dirdat\lt
```
Remove the RMTHOST parameter.
Save and close the file.
Add a new data-pump Extract group, using the trail that you specified in step 2 as the data source.
```
ADD EXTRACT group, EXTTRAILSOURCE trail
```
For example:
```
ADD EXTRACT pump, EXTTRAILSOURCE dirdat\lt
```
Create a parameter file for the new data pump.
```
EDIT PARAMS group
```
In the parameter file, include the appropriate Extract parameters for your configuration, plus:
- TABLE parameter(s) for the tables that are to be processed by this data pump.
- RMTHOST parameter to point to the target system.
- RMTTRAIL parameter to point to a new remote trail (to be created later).
In GGSCI on the source system, add a remote trail for the data-pump. Use the trail name that is specified with RMTTRAIL in the data pump's parameter file, and specify the group name of the data pump for EXTRACT.
```
ADD RMTTRAIL trail, EXTRACT group
```
For example:
```
ADD RMTTRAIL dirdat/rt, EXTRACT pump
```
Note:

This command binds a trail name to an Extract group but does not actually create the trail. A trail file is created when processing starts.
On the target system, run GGSCI.

Add a new Replicat group and link it with the remote trail.

ADD REPLICAT group, EXTTRAIL trail

For example:

ADD REPLICAT rep, EXTTRAIL dirdat/rt

Create a parameter file for this Replicat group. You can copy the parameter file from the original Replicat group, but make certain to change the REPLICAT parameter to the new group name.
On the source system, stop the primary Extract group, then start it again so that the parameter changes you made take effect.
```
STOP EXTRACT group
START EXTRACT group
```
On the source system, start the data pump.
```
START EXTRACT group
```
On the target system, issue the LAG REPLICAT command for the old Replicat, and continue issuing it until it reports At EOF, no more records to process.
```
LAG REPLICAT group
```
Stop the old Replicat group.
```
STOP REPLICAT group
```
If using a checkpoint table for the old Replicat group, log into the database from GGSCI.
```
DBLOGIN [SOURCEDB datasource] [{, USERIDALIAS alias | USERID user [,options]]
```
Delete the old Replicat group.
```
DELETE REPLICAT group
```
Start the new Replicat group.
```
START REPLICAT group
```
Note:

Do not delete the old remote trail, just in case it is needed later on for a support case or some other reason. You can move it to another location, if desired.