【OGG】关于在一套复制环境中使用不同版本OGG的问题
【OGG】关于在一套复制环境中使用不同版本OGG的问题
1.源头OGG版本低,目的端OGG版本高,此种配置不需要做任何的额外改动.跟两端是相同OGG版本的同步是完全一样的参数设置.
2.源头OGG版本高,目的端OGG版本低,此种配置需要在源头的抽取进程和传输进程的参数文件中设置trailfile的格式(设置为跟目的端OGG版本一样的格式).
EXTTRAIL <trail file>, FORMAT RELEASE 10.0RMTTRAIL <trail file>, FORMAT RELEASE 10.0注意:此处的10.0是目的端OGG的版本号.
3.源头的抽取进程和传输进程的参数文件中务必都要设置trailfile的格式.因为,仅仅依靠传输进程无法达到转换trailfile格式的目的.因为传输进程就是这么设计的:It must write trails in the same version it read them.
参考文章:
different versions of golden gate (社区论坛 ID 3570021)
Can OGG Version 11 Be Used to Pump/Move Trails Generated from Version 9 or 10? (文档 ID 1297283.1)
Can OGG Version 11 Be Used to Pump/Move Trails Generated from Version 9 or 10? (文档 ID 1297283.1)
类型: 状态: 上次主更新: 上次更新: |
HOWTOARCHIVED2014-12-152017-2-6 |
In this Document
Goal |
Solution |
APPLIES TO:
Oracle GoldenGate - Version 11.1.1.0.0 and later
Information in this document applies to any platform.
GOAL
Can Oracle GoldenGate version 11 Extract be used to pump/move trail files which were generated from version 9 or 10 to another server?
SOLUTION
Oracle GoldenGate version 11.1 can read versions 9 and version 10 trail files but it can not write them in a different format (version 11.1) than the version of the trail being read. It must write trails in the same version it read them. The extract can be forced to write a trail in a particular version format by using the FORMAT RELEASE option.
Example:
RMTTRAIL <trail file>, FORMAT RELEASE 10.0
©著作权归作者所有:来自51CTO博客作者小麦苗DB宝的原创作品,如需转载,请注明出处,否则将追究法律责任
更多相关文章
- 使用shell脚本监控Linux主机
- DM8->KAFKA部署手册
- Gitblit版本服务器环境部署记录
- IntelliJ IDEA 2021.1 破解,IDEA 2021.1激活破解,激活持续更新
- 支付宝支付--沙箱支付教程+案例 | PC端网站支付(超级详细版本)
- Spark Delta Lake 0.4.0 发布,支持 Python API 和部分 SQL
- PyCharm2021最新激活教程激活码(PyCharm 2020.3最新版本实测有效)
- Redis 6.0 稳定版发布,支持多线程 IO
- Docker安装及配置优化(3)