一、需求,Oracle Db 11.2.0.1 ->Db19.3 pdb 使用Ogg 同步
根據上述需求！
二、問題
這個需求取決於很多客戶想上19c了，ogg屬於可以0停機視窗|跨平臺|跨字符集|跨資料庫版本，多個優點於一體的遷移升級方案！
使用Oracle Db 10.2.0.5 <=> Oracle Db 19.3,ogg 如何配置？
使用Oracle Db 11.2.0.1 ,ogg 11.2 <=> Oracle Db 19.3 ,ogg 19.1 能否進行雙向同步？
使用Oracle Db 11.2.0.4 <=> Oracle Db 19.3,ogg 又如何配置呢？
根據上述問題，查詢相關資料，對部分進行測試整理。
三、版本相關資料
https:https:OGG-06221源容器資料庫需要Trail FORMAT .3或更高版本（文件ID -OGG-01332檔案xxx與當前軟體版本的相容性級別5不相容。（Doc ID -01332的複製異常終止與當前軟體版本的相容級別5不相容。（文件ID
3.1）19.1 ogg 官方文件,描述12.2 DB版本OGG 最低版本相容性
The following settings are supported Oracle Database non-CDB or higher with compatibility to , FORMAT RELEASE or above non-CDB or higher with compatibility to , FORMAT RELEASE or above CDB/PDB or higher with compatibility to , only FORMAT RELEASE values or higher are supported. This due to the use of local undo PDBs, which requires augmenting the transaction ID with the PDB number to ensure uniqueness of trx IDs. FOr DB >=12.2,compatibility <=12.2 AND NO PDB ,OGG 最低的format release 12.2! 上述版本 AND PDB ! 最低format release 12.3!!!
3.2） MOS 2315957.1，DB 12.2 PDB 使用OGG 能不能降低到12.2 ？
Source: Oracle Database .. Multitenant - OGG version . - OGG version -- :: ERROR OGG- File ./dirdat/HIPOS/mb000000001, with compatibility level , not compatible with the current software versions parameter file to generate the appropriate format the FORMAT LEVEL so that Replicat doesn<Extract name>/dirdat/ea, FORMAT RELEASE <Pump>/dirdat/ra, FORMAT RELEASE - Source container database requires trail FORMAT ) Pump would run fine although trail format still remains since Source Extract never was never able to convert the format to - Output file ./dirdat/HIPOS/mb format RELEASE RDBMS binary requires trail format to be format trails when running against Oracle Database with CDB/PDB 本例中DB 12.2 ,COM 12.2,PDB OGG 12.3 抽取程式，投遞程式版本都降低為12.2 ！！！ 但是複製程式報錯，提升版本level =6,需要降低為level 5才ok mos給出了說法！ pdb like local undo trail format to be 12.3 !!! 引數寫12.2沒有用！
3.3） 2316837.1，源端12.2,目標端12.3，低到高版本，低版本指定release 12.2 的情況
.. (source) and (target) with the following parameter starting pump fails with the following errors and it /ex, format release /ms, format release -- :: INFO OGG- Remote Collector/Server version receiving data a different version than Extract -- :: INFO OGG- Socket buffer size to (flush size -- :: INFO OGG- Recovery initialization completed target file dirdat/ms000000000, at RBA -- :: INFO OGG- Output file dirdat/ms format RELEASE -- :: ERROR OGG- File dirdat/ms000000000, with compatibility level , not compatible with the current software versions parameter file to generate the appropriate format the FORMAT LEVEL -- :: ERROR OGG--WJ-DB) ><PUMP-NAME> :: ::<EXTRACT-NAME> :: :: you use parameter FORMAT RELEASE when source GG version not have to use FORMAT RELEASE parameter when source GG version (Example: ) ) so remove the parameter extract/pump parameter file and then re-/or the document content above, the user information and data used represents fictitious data purely coincidental and not intended any manner. 這個案例也很有意思！
12.2.0.1.0 (source) and 12.3 (target) with the following "format release" 就是源端ogg 版本12.2.0.1 ->目標端ogg 12.3，低版本到高版本，並且抽取投遞程式中都使用了版本release 12.2！！！ 但是複製程式報錯！ 官方的意思就是，低版本的檔案，到高版本Ogg去應用，無需使用版本引數，畫蛇添足！ 重點，低到高無需進行版本轉換！
3.4 ） 1451840.1， Ogg 11.2 源端抽取的trail的檔案ogg 11.1 ， 10.4無法解析
GoldenGate Replicat abend with -- :: ERROR OGG- File dirdat\pj000088, with compatibility level , not compatible with the current software versions parameter file to generate the appropriate format the FORMAT LEVEL -- :: GGS ERROR ZZ-0QE File header failed to parse tokens. File dirdat\pj000025, last offset , data: and old OGG versions ( v11. / )are different and so a replicat running with OGG v11. / cannot read a trail file written by extract / lower than and the source OGG v11., we need to use the FORMAT RELEASE parameter running with OGG v11. and the target running with OGG v11./pj, format release --------- been encountered when doing the initial load, we need to add the
3.5） 2385520.1，Db12.2c Ogg 12.3 to Db11g Ogg 12.2 ，同步是否有什麼問題？？？
.. and .... OGGCORE_12.. ::.. OGGCORE_12.., ppc, 64bit (optimized), Oracle 11g on Jul :: -up . database abends with error: ERROR OGG- File /dirdat/rt000000000, with compatibility level , not compatible with the current software versions parameter file to generate the appropriate format the FORMAT LEVEL and on target database . The trail files which are written RDBMS binary requires trail format to be . Hence Extract has to use format trails when running against Oracle Database with CDB/ on version on the target ) Set up a remote replicat to replicat changes the multitenant database to the ) Set up a middle tier database. Use database to setup a downstream mining environment to extract data the CDB. OGG can be used on the downstream mining database and the trails format can be transported to the source database ) Set source redo compatibility on DB to . Once the redo compatibility , you can use OGG with the DB well 本例中：Db12.2c Ogg 12.3 to Db11g Ogg 12.2 複製程式abend提示 版本level6 ,需要降低1個版本到Level 5 官方建議： 1.都使用同一個OGG 12.3 這樣就不存在Ogg產生的trail檔案版本問題了； 2.對抽取程式的12.3 OGG軟體上面，配置一個遠端複製，這樣就不存在版本的問題了； 3.配置一箇中間伺服器,第一條鏈路 DB 12.2 Ogg 12.3 -> 中間庫DB 11g or 12c; 第二條鏈路 DB 11g or 12c OGG 12.2 ->目標庫11.2.0.4 ； 4.將資料庫相容性版本設定為12.1 ！！！ Set source redo compatibility on 12.2 DB to 12.1
四、場景測試
4.1 Source Db 19.3 Ogg 19.1 toTarget Db11.2.0.4 Ogg 11.1
ERROR OGG-00664 OCI Error during OCIServerAttach (status = 12162-Error while trying to retrieve text for error ORA-12162). $ oerr ora 1216212162, 00000, "TNS:net service name is incorrectly specified"// *Cause: The connect descriptor corresponding to the net service name in// TNSNAMES.ORA or in the directory server (Oracle Internet Directory) is// incorrectly specified.// *Action: If using local naming make sure there are no syntax errors in// the corresponding connect descriptor in the TNSNAMES.ORA file. If using// directory naming check the information provided through the administration// used for directory naming.報錯，配置檔案中沒有使用tns遠端的方式！ 無解
4.2 Source Db 19.3 Ogg 19.1 toTarget Db11.2.0.4 Ogg 12.2
>/u01/ogg1//dirdat/t2utf8/t1/t1,format release -- :: ERROR OGG- Source container database requires trail FORMAT / or higher. 抽取程式投遞程式降低版本到12.3，複製程式依然報錯！
ERROR OGG-01332 File /home/oggtest2/base/dirdat/t1/t1000000000, with compatibility level 7, is not compatible with the current sof
tware version's compatibility level of 5. Modify the file writer's parameter file to generate the appropriate format using the FORMAT LEVEL 5 option.
4.3 Source Db 19.3 Ogg 19.1 toTarget Db11.2.0.4 Ogg 12.3
源端
EXTTRAIL /u01/ogg1/base/dirdat/t2utf8/t1/t1 ,FORMAT RELEASE 12.3
rmttrail /home/oggtest3/base/dirdat/t1/t1 ,FORMAT 12.3
> unregister extract ext_t1 database
> register extract ext_t1 database CONTAINER(pdbodb)
OGG-01232 Receive TCP params error: TCP/IP error 104 (Connection reset by peer), endpoint:
> alter EXTRACT DP_T3,etrollover
抽取程式、投遞程式均進行版本降級處理！ 抽取程式遇到600無處理方法，刪除重建程式重新註冊；
投遞程式投遞寫入可能需要使用引數重新寫入，版本修改後，寫入的檔案可能需要重新覆蓋寫入目標端
- File /home/oggtest3//dirdat/t1/t1000000000, with trail format release LEVEL , s parameter file to generate the appropriate format > alter REPLICAT rep_t3,extseqno ,extrba
4.4 Source Db 10.2.0.5 Ogg 11.1 toTarget Db19.2 Ogg 19.1
-
五、OGG Trail檔案從6位轉換為9位,我們需要注意些什麼，什麼版本引入的改變？
5.1) OGG什麼版本Trail檔案位數轉換為9位？
ogg11.- File <filename>, with compatibility level , not compatible with the current software versionOracle GoldenGate - Version .. to .. [Release to - File <filename>, with compatibility level , not compatible with the current software version any OGG version target OGG version lower than source , only compatibility value will change target OGG version or prior , please add TRAIL_SEQLEN_6D parameter GLOBALS file of source GGSCI , logout/login of ggsci , restart manager and re-create extract / pump process 這篇文件告訴了我們，第一確認了上述第四部分，OGG目標端比源端OGG版本低的情況下,源端必須降低版本到目標端相同的版本，才能進行復制使用！ 反向低到高不存在啥子問題！ 另外一個特性就是OGG12.1以及它之前，抽取的位數還是6位！ 如果要給12.1以及更早版本OGG使用，除了降低版本相容性之外！ 還需要全域性引數新增！
TRAIL_SEQLEN_6D 已確保，抽取程式抽取的位數使用6位！！！
5.2) OGG12.1 ->OGG12.2 複製程式不報錯但是不同步資料！
Replicat checkpoint shows digit trail file instead of digits when source OGG version .x and target OGG version .x (Doc ID .. version, ---------------- running but not applying any data when replicat source OGG version ..x to .----------------------- caused due to following setup : Source and target . Pump generate digit trail seqno and replicat was configured to use and target . When adding the replicat, the checkpoint should be take . edit ./--. ggsci><replicat_name> EXTTRAIL /bscs_dumps/oracle/ggtrails/dirdat/ seqno and RBA . If seqno not available, you may need to alter the replicat to least available seqno. Eg: If the trail file available <replicat_name>, extseqno , extrba - Oracle GoldenGate Best Practice: NFS Mount options use with GoldenGate 正常情況下，OGG源端低版本，OGG目標端高版本應用是沒有任何問題對吧？ 但是12.1=>12.2 ogg是，複製程式不報錯，但是不應用資料！ 什麼原因呢？ 12.1抽取的檔案格式6位，12.2OGG版本識別的檔案是Trail 9位！ 解決辦法就是目標端12.2 OGG mgr程式編輯引數，降低自己識別的位數！TRAIL_SEQLEN_6D
|
ERROR OGG-06601 Mismatch Between The Length Of Seqno From Checkpoint (9) And Recovery (6) For Ext (Doc ID 2181389.1)
|
5.3)關於位數問題，我們需要關注什麼？
第一、對於12.1->12.2 ogg的同步需要參考MOS；
第二、由於4部分進行了測試11.1 ogg ->19.1 ogg同步無異常！ 因此可以說明Oracle在較高的版本已經自己修復了這個位數不同導致,低->高版本不相容的問題！
第三、基於上述情況，只要不報錯就不處理！
低到高，目標端高版本的OGG軟體,global引數設定降低為6位，應用trail檔案！
高到低，源端設定global，降低為6位進行抽取及投遞，目標端低版本本身就是6位無需調整；
原文地址：https://www.cnblogs.com/lvcha001/p/14762355.html