Adding Another Replicat Group to an Active Configuration

This procedure adds a new Replicat group to an existing Replicat group. The new Replicat reads from the same trail as the original Replicat.

Multiple Replicat groups may be required when Replicat is configured in classic mode, for the purpose of isolating transactions on certain tables or improving performance. Multiple Replicat groups usually are not required if using coordinated Replicat, because you can divide the workload among multiple processing threads within the same Replicat group. See Creating an Online Replicat Group for more information about Replicat modes.

Steps are performed on the source and target systems.

Choose a name for the new group.
On the target system, run GGSCI.
Create a parameter file for the new Replicat group.
```
EDIT PARAMS group
```
Note:

You can copy the original parameter file to use for this group, but make certain to change the Replicat group name and any other relevant parameters that apply to this new group.
Add MAP statements (or edit copied ones) to specify the tables that you are adding or moving to this group. If this group will be a coordinated Replicat group, include the appropriate thread specifications.
Save and close the parameter file.
On the source system, run GGSCI.
Stop the Extract group.
```
STOP EXTRACT group
```
Issue the INFO REPLICAT command for the old Replicat group, and continue issuing it until it reports At EOF, no more records to process.
```
INFO REPLICAT group
```
On the target system, edit the old Replicat parameter file to remove MAP statements that specified the tables that you moved to the new Replicat group. Keep only the MAP statements that this Replicat will continue to process.
Save and close the file.
Issue the INFO REPLICAT command for the old Replicat group, and continue issuing it until it reports At EOF, no more records to process.
```
INFO REPLICAT group
```
Obtain the current Replicat checkpoint.

INFO REPLICAT group
Stop the old Replicat group. If you are stopping a coordinated Replicat, make certain the stop is clean so that all threads stop at the same trail record.
```
STOP REPLICAT group
```
Alter the new Replicat to position at the same trail sequence number and RBA as the old replicat group

ALTER REPLICAT group, EXTSEQNO seqno, EXTRBA rba

The seqno is the trail sequence number from the old group checkpoint and the rba is the trail record RBA number from the old group checkpoint.
Add the new Replicat group. For EXTTRAIL, specify the trail that this Replicat group is to read.
```
ADD REPLICAT group, EXTTRAIL trail
```
For example:
```
ADD REPLICAT rep, EXTTRAIL dirdat/rt
```
Issue the INFORM COMMAND to alter the Replicat to the trail file sequence number and RBA displayed.
```
INFORM COMMAND
```
On the source system, start the Extract group.
```
START EXTRACT group
```
On the target system, start the old Replicat group.
```
START REPLICAT group
```
Start the new Replicat group.
```
START REPLICAT group
```