Impact of DDL Change on TRANDATA
edited Dec 22, 2013 3:22AM in GoldenGate, Streams and Distributed Database (MOSC) 2 commentsAnswered ✓
SITUATIONGoldengate 11.2.1.0.14, RDBMS 11gR2.
GG is not configured to manage DDL. We have to manually make DDL changes on the source and coordinate them with changes on the target.
All tables in the schema have supplemental logging and TRANDATA
If I add a column, I'm assuming that I have to re-run the TRANDATA command. The problem is, when I simply add a column and rerun the ADD TRANDATA command, it errors out telling me trandata has already been added. So I am left with having to:
I am concerned about the time that trandata is left off the table during step 2 while the database is fully operational.
GG is not configured to manage DDL. We have to manually make DDL changes on the source and coordinate them with changes on the target.
All tables in the schema have supplemental logging and TRANDATA
If I add a column, I'm assuming that I have to re-run the TRANDATA command. The problem is, when I simply add a column and rerun the ADD TRANDATA command, it errors out telling me trandata has already been added. So I am left with having to:
1. delete trandata for the table
2. add the column
3. re-add trandata for the table
2. add the column
3. re-add trandata for the table
I am concerned about the time that trandata is left off the table during step 2 while the database is fully operational.
0