OGG

2023-11-30 16:26| 来源: 网络整理| 查看: 265

一、需求,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://blog.csdn.net/ghostliming/article/details/72830291 https://www.cnblogs.com/margiex/p/7865024.html OGG-06221源容器数据库需要Trail FORMAT 12.3或更高版本（文档ID 2315957.1）兼容性级别为6的Pump abend-OGG-01332文件xxx与当前软件版本的兼容性级别5不兼容。（Doc ID 2316837.1）兼容级别为6的错误OGG-01332的复制异常终止与当前软件版本的兼容级别5不兼容。（文档ID 2385520.1） GoldenGate Replicat abend with "OGG-01332 File dirdat\xx, with compatibility level 3, is not compatible with the current software version's compatibility level of 2 (Doc ID 1451840.1) https://docs.oracle.com/en/middleware/goldengate/core/19.1/gclir/add-exttrail.html#GUID-C3330B6A-9514-4015-996E-2461BE36273D 3.1）19.1 ogg 官方文档,描述12.2 DB版本OGG 最低版本兼容性 The following settings are supported for Oracle Database 12.2 and higher: For Oracle Database 12.2 non-CDB or higher with compatibility set to 12.1, FORMAT RELEASE 12.2 or above is supported. For Oracle Database 12.2 non-CDB or higher with compatibility set to 12.2, FORMAT RELEASE 12.2 or above is supported. For Oracle Database 12.2 CDB/PDB or higher with compatibility set to 12.2, only FORMAT RELEASE values 12.3 or higher are supported.This is due to the use of local undo for PDBs, which requires augmenting the transaction ID with the PDB number to ensure uniqueness of trx IDs.

FOr DB >=12.2,compatibility 中间库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 12162 12162, 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 > start ext_t1 EXTTRAIL /u01/ogg1/base/dirdat/t2utf8/t1/t1,format release 12.2 2021-05-12 04:26:07 ERROR OGG-06221 Source container database requires trail FORMAT 12.3/18.1 or higher.抽取进程投递进程降低版本到12.3，复制进程依然报错！

ERROR OGG-01332 File /home/oggtest2/base/dirdat/t1/t1000000000, with compatibility level 7, is not compatible with the current software 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无处理方法，删除重建进程重新注册；

投递进程投递写入可能需要使用参数重新写入，版本修改后，写入的文件可能需要重新覆盖写入目标端

需要alter 指定使用版本后的文件，否则默认还是使用之前老的版本，则报错 ERROR OGG-02598 File /home/oggtest3/base/dirdat/t1/t1000000000, with trail format release LEVEL 7, is not compatible with the current software version's trail file format release RELEASE 12.3. Modify the file writer's parameter file to generate the appropriate format using the FORMAT RELEASE RELEASE 12.3 option. GGSCI (t1) 9> alter REPLICAT rep_t3,extseqno 1,extrba 0

4.4 Source Db 10.2.0.5 Ogg 11.1 toTarget Db19.2 Ogg 19.1

复制进程参数需要使用 assumetargetdefs 否则可能会报OGG-00423OGG可以正向传输！！！低版本->高版本，没啥子问题，没毛病！

五、OGG Trail文件从6位转换为9位,我们需要注意些什么，什么版本引入的改变？ 5.1) OGG什么版本Trail文件位数转换为9位？ ogg11.1 t1000000 ogg19.1 ta000000000 Goldengate Replicat Process Abending With ERROR OGG-01332 File , with compatibility level 6, is not compatible with the current software version's compatibility level of 4 (Doc ID 2538448.1) Oracle GoldenGate - Version 12.1.2.1.0 to 18.1.0.0.0 [Release 12.1 to 12.2] Goldengate Replicat Process Abending With ERROR OGG-01332 File , with compatibility level 6, is not compatible with the current software version's compatibility level of 4 CAUSE Customer was using lower target OGG version than source OGG version This error can occur for any OGG version if target OGG version is lower than source , only compatibility value will change for different OGG versions SOLUTION Please add FORMAT RELEASE parameter in extract or pump Additionally if target OGG version is 12.1 or prior , please add TRAIL_SEQLEN_6D parameter in 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 9 digit trail file instead of 6 digits when source OGG version is 12.1.x and target OGG version is 12.2.x (Doc ID 2120995.1) SYMPTOMS On : 12.2.0.1.0 version, 1 - Oracle DB backend ACTUAL BEHAVIOR --------------- Replicat is running but not applying any data when replicat from source OGG version 12.1.2.0.x to 12.2.0.x EXPECTED BEHAVIOR ----------------------- Replicat is running but not applying any data to target side. CAUSE This is caused due to following setup : Source is 12.1 and target is 12.2. Pump generate 6 digit trail seqno and replicat was configured to use 9 digit. When source is 12.1 and target is 12.2. When adding the replicat, the checkpoint should be take 6 digit trail file. SOLUTION 1. edit params ./GLOBALS --Add the following parameter and save the file TRAIL_SEQLEN_6D 2. stop mgr 3. exit 4. ggsci>start mgr 5. dblogin userid , password 6. Add the replicat ADD REPLICAT EXTTRAIL /bscs_dumps/oracle/ggtrails/dirdat/bt ,checkpointtable ggadmin.checkpoint. The above command will make the replicat to start from seqno 0 and RBA 0. If seqno is not available, you may need to alter the replicat to least available seqno. Eg: If the trail file available is bt000001, then you need to alter the replicat like the following dblogin userid , password alter replicat , extseqno 1, extrba 0 NOTE: Customers running GoldenGate for Teradata may need to perform the same steps a couple of times before it works. If steps do not work the first time then logout ggsci prompt, enter ggsci prompt, execute steps above again and check point accepts6 digit trail file. NOTE:1232303.1 - Oracle GoldenGate Best Practice: NFS Mount options for use with GoldenGate

正常情况下，OGG源端低版本，OGG目标端高版本应用是没有任何问题对吧？但是12.1=>12.2 ogg是，复制进程不报错，但是不应用数据！什么原因呢？ 12.1抽取的文件格式6位，12.2OGG版本识别的文件是Trail 9位！解决办法就是目标端12.2 OGG mgr进程编辑参数，降低自己识别的位数！TRAIL_SEQLEN_6D

5.3)关于位数问题，我们需要关注什么？

第一、对于12.1->12.2 ogg的同步需要参考MOS；

第二、由于4部分进行了测试11.1 ogg ->19.1 ogg同步无异常！因此可以说明Oracle在较高的版本已经自己修复了这个位数不同导致,低->高版本不兼容的问题！

第三、基于上述情况，只要不报错就不处理！

低到高，目标端高版本的OGG软件,global参数设置降低为6位，应用trail文件！

高到低，源端设置global，降低为6位进行抽取及投递，目标端低版本本身就是6位无需调整；

【本文地址】

公司简介

联系我们