【OGG】關於在一套複製環境中使用不一樣版本OGG的問題

時間 2021-04-11

標籤 app ide this spa 設計 orm server 進程文檔同步欄目 Java 简体版

原文原文鏈接

【OGG】關於在一套複製環境中使用不一樣版本OGG的問題

1.源頭OGG版本低,目的端OGG版本高,此種配置不須要作任何的額外改動.跟兩端是相同OGG版本的同步是徹底同樣的參數設置.

2.源頭OGG版本高,目的端OGG版本低,此種配置須要在源頭的抽取進程和傳輸進程的參數文件中設置trailfile的格式(設置爲跟目的端OGG版本同樣的格式).app

EXTTRAIL <trail file>, FORMAT RELEASE 10.0

RMTTRAIL <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)ide

Can OGG Version 11 Be Used to Pump/Move Trails Generated from Version 9 or 10? (文檔 ID 1297283.1)

this

類型: 狀態: 上次主更新: 上次更新:

HOWTOARCHIVED2014-12-152017-2-6

In this Documentspa

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?orm

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:server

RMTTRAIL <trail file>, FORMAT RELEASE 10.0進程