Coordinating Table Attributes between Source and Target

Follow this procedure if you are changing an attribute of a source table that is in the Oracle GoldenGate configuration, such as adding or changing columns or partitions, or changing supplemental logging details (Oracle). It directs you how to make the same change to the target table without incurring replication latency.

Note:

This procedure assumes that the Oracle GoldenGate DDL support feature is not in use, or is not supported for your database. For Oracle and MySQL databases, you can enable the DDL support feature of Oracle GoldenGate to propagate the DDL changes to the target, instead of using this procedure.

On the source and target systems, create a table, to be known as the marker table, that can be used for the purpose of generating a marker that denotes a stopping point in the transaction log. Just create two simple columns: one as a primary key and the other as a regular column. For example:
```
CREATE TABLE marker
(
id int NOT NULL,
column varchar(25) NOT NULL,
PRIMARY KEY (id)
);
```
Insert a row into the marker table on both the source and target systems.
```
INSERT INTO marker VALUES (1, 1);
COMMIT;
```
On the source system, run GGSCI.
Open the Extract parameter file for editing.

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..
Add the marker table to the Extract parameter file in a TABLE statement.
```
TABLE marker;
```
Save and close the parameter file.
Add the marker table to the TABLE statement of the data pump, if one is being used.
Stop the Extract and data pump processes, and then restart them immediately to prevent capture lag.
```
STOP EXTRACT group
START EXTRACT group
STOP EXTRACT pump_group
START EXTRACT pump_group
```
On the target system, run GGSCI.
Open the Replicat parameter file for editing.

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.
Add the marker table to the Replicat parameter file in a MAP statement, and use the EVENTACTIONS parameter as shown to stop Replicat and ignore operations on the marker table.
```
MAP marker, TARGET marker, EVENTACTIONS (STOP, IGNORE);
```
Save and close the parameter file.
Stop, and then immediately restart, the Replicat process.
```
STOP REPLICAT group
START REPLICAT group
```
When you are ready to change the table attributes for both source and target tables, stop all user activity on them.
On the source system, perform an UPDATE operation to the marker table as the only operation in the transaction.
```
UPDATE marker
SET column=2,
WHERE id=1;
COMMIT;
```
On the target system, issue the following command until it shows that Replicat is stopped as a result of the EVENTACTIONS rule.
```
STATUS REPLICAT group
```
Perform the DDL on the source and target tables, but do not yet allow user activity.
Start Replicat.
```
START REPLICAT group
```
Allow user activity on the source and target tables.