Goldengate: How To Handle resize a column when not using DDL replication?

Resize a column when not using DDL replication

1. If the resized column is a key column, make sure there are no open transactions on the affected source table between step 2 & 6.

2. Issue LAG EXTRACT. When Extract's lag is 0... or... at EOF, stop Extract.

GGSCI (source.doy.com) > lag extract ext1
Sending GETLAG request to EXTRACT ext1...
No records yet processed.
At EOF, no more records to process.

GGSCI (source.doy.com) > stop extract ext1

3. (If pump is in use) Issue LAG EXTRACT for the pump. When the pump's lag is 0... or... at EOF..

GGSCI (source.doy.com) > lag extract dpump1
GGSCI (source.doy.com) > stop extract dpump1

4. Issue LAG REPLICAT. When Replicat's lag is 0... or... at EOF...
GGSCI (target.doy.com) > lag replicat rep1
GGSCI (target.doy.com) > stop replicat rep1

5. Resize the column in both the source and target tables.

SQL> alter table sample modify (col2 varchar2(5));
Table altered.
SQL> alter table sample modify (col2 varchar2(5));
Table altered.

6. Issue ALTER EXTRACT for Extract to switch to a new trail file, then start Extract.

GGSCI (source.doy.com) > start extract ext1

7. (If pump is in use) Issue ALTER EXTRACT for the pump to switch to a new remote trail file, then start the pump.

GGSCI (source.doy.com) > start extract dpump1

8. Alter Replicat to start at the beginning of the new remote trail file, then start Replicat.

GGSCI (target.doy.com) > alter replicat <rep1>, extseqno , extrba 0
GGSCI (target.doy.com) > start replicat <rep1>