Question:gg only config to replicate dml, when source has some ddl changes, how to handle in source and target?
Answer:
GoldenGate capture the dml changes only by default,if you have made any changes in DDL structure,then stop the extract and replicat process and make changes in DDL structure and restart the extract and replicat process,then only extract can be able to capture the changes done at DDL structure.
It is advisible that stop extract,pump and replicat process make changes in the DDL and restart the extract,pump and replicat.
The above suggested procedure will not make any impact in DDL replication.
Also you can follow the below procedure
1. stop extract
2. stop data pump
3. there are lag in replicat, so replicat still running to reduce lag
4. do ddl in source, when replicat is running
5. stop replicat untill lag=0
6.do ddl in target
7.start extract and pump and replicat
Question:After do ddl in source, whether need to do delete and re-add the trandata on the table which is been changed?
Answer:
yes,you are correct,After doing DDL changes,you need to do delete and re-add the trandata on the table which is being changed.
© 2010, www.oracledatabase12g.com. 版权所有.文章允许转载,但必须以链接方式注明源地址,否则追究法律责任.
相关文章 | Related posts:
- GoldenGate实现Live Standby主备库切换(2)
- How to create a GoldenGate uni-directional target database in a production database zero downtime
- GoldenGate实现Live Standby主备库切换(1)
- How to understand goldengate report file statistics
- Compare and Converge in an Oracle Streams Replication Environment
- Goldengate can’t extract data from compressed table
- Oracle GoldenGate: Disaster Recovery Solution
- How To Exclude A Table From Schema Capture And Replication When Using Schema Level Streams Replication
- Goldengate一个令人郁闷的小细节
- 配置GoldenGate同步DDL语句(2)




Thanks a lot Dear ! it helps a lot