mos文章将ogg捕捉模式由普通模式转换成集成捕捉
2017-07-19 14:42
316 查看
How To Upgrade From Goldengate Classic Extract To Integrated Extract (文档 ID 1484313.1) 转
--------------------------------------------------------------------------------
In this Document
Goal
Solution
References
--------------------------------------------------------------------------------
Applies to:
Oracle GoldenGate - Version 11.2.1.0.0 and later
Information in this document applies to any platform.
Goal
Steps to upgrade a Goldengate classic extract to integrated extract
Solution
To run integrated extract in 11.2.1 Goldengate , the following requirements should be met
1.Oracle RDBMS must be 11.2.0.3 or higher
and
2.You must apply the RDBMS(Database) patches as suggested in the below MOS document
NOTE:1411356.1 - 11.2.0.3 Database specific bundle patch for Integrated Extract 11.2.x
The redo compatibility should be set to 11.2.0.3 matching the db version.
3. NOTE: STEP 3 IS SPECIFIC TO RAC ENVIRONMENTS AND OGG VERSIONS 11.2.1.0.23+. If using OGG version prior to 11.2.1.0.23 step 3 can be skipped.
To overcome below bug 18103455 OGG versions 11.2.1.0.23+ introduces a new TRANLOPTIONS option PREPAREFORUPGRADETOIE and a change to the procedure for switching from classic to integrated Extract.
Bug 18103455 – Replicat abends with “WARNING OGG-01154 SQL error 1403 mapping” because of missing data that extract skipped during a change from classic Extract to Integrated Extract.
A) For a running extract, issue the following command:
SEND extract <extract name> tranlogoptions prepareforupgradetoie
B) For a stopped extract, start it after adding the following line to the parameter file:
TRANLOGOPTIONS PREPAREFORUPGRADETOIE
C) Monitor the ggserr.log file or corresponding extract report file for an INFO GG-01873 message indicating the the change has taken affect and that you can proceed with the upgrade.
Example from report file:
2014-06-05 17:06:09 INFO OGG-01873 The parameter TRANLOGOPTIONS PREPAREFORUPGRADETOIE has taken effect. Proceed to the next step in the upgrade process.
Example from ggserr.log file:
2014-06-05 17:06:09 INFO OGG-01873 Oracle GoldenGate Capture for Oracle, src.prm: The parameter TRANLOGOPTIONS PREPAREFORUPGRADETOIE has taken effect.
For the INFO message to show up extract has to process a committed transaction on all the RAC nodes for a table being captured. As an alternative a dummy table can be added
to the extract parameter file and doing DML on this table from all the threads would give extract commit boundary current checkpoints for all the threads
D) Once said message is detected, Stop the extract, perform dblogin, and alter for conversion to Integrated as shown below
4.
Connect to the Extract database, and grant the following priviege to GG Admin user
SQL>exec dbms_goldengate_auth.grant_admin_privilege('OGG_TS');
Login into GGSCI?Check to see if upgrade possible
GGSCI> DBLOGIN USERID <ID> PASSWORD <PW>
GGSCI> INFO <extract_name> UPGRADE
Upgrade may fail, in case of existing open transactions
GGSCI>stop extract <extract_name>
GGSCI>dblogin userid <ggadmin>,password <password>
--Register the extract in the database if not done already
GGSCI>register extract <extract_name> database
GGSCI>alter extract <extract_name>,upgrade integrated tranlog
GGSCI>start extract <extract_name>
--------------------------------------------------------------------------------
In this Document
Goal
Solution
References
--------------------------------------------------------------------------------
Applies to:
Oracle GoldenGate - Version 11.2.1.0.0 and later
Information in this document applies to any platform.
Goal
Steps to upgrade a Goldengate classic extract to integrated extract
Solution
To run integrated extract in 11.2.1 Goldengate , the following requirements should be met
1.Oracle RDBMS must be 11.2.0.3 or higher
and
2.You must apply the RDBMS(Database) patches as suggested in the below MOS document
NOTE:1411356.1 - 11.2.0.3 Database specific bundle patch for Integrated Extract 11.2.x
The redo compatibility should be set to 11.2.0.3 matching the db version.
3. NOTE: STEP 3 IS SPECIFIC TO RAC ENVIRONMENTS AND OGG VERSIONS 11.2.1.0.23+. If using OGG version prior to 11.2.1.0.23 step 3 can be skipped.
To overcome below bug 18103455 OGG versions 11.2.1.0.23+ introduces a new TRANLOPTIONS option PREPAREFORUPGRADETOIE and a change to the procedure for switching from classic to integrated Extract.
Bug 18103455 – Replicat abends with “WARNING OGG-01154 SQL error 1403 mapping” because of missing data that extract skipped during a change from classic Extract to Integrated Extract.
A) For a running extract, issue the following command:
SEND extract <extract name> tranlogoptions prepareforupgradetoie
B) For a stopped extract, start it after adding the following line to the parameter file:
TRANLOGOPTIONS PREPAREFORUPGRADETOIE
C) Monitor the ggserr.log file or corresponding extract report file for an INFO GG-01873 message indicating the the change has taken affect and that you can proceed with the upgrade.
Example from report file:
2014-06-05 17:06:09 INFO OGG-01873 The parameter TRANLOGOPTIONS PREPAREFORUPGRADETOIE has taken effect. Proceed to the next step in the upgrade process.
Example from ggserr.log file:
2014-06-05 17:06:09 INFO OGG-01873 Oracle GoldenGate Capture for Oracle, src.prm: The parameter TRANLOGOPTIONS PREPAREFORUPGRADETOIE has taken effect.
For the INFO message to show up extract has to process a committed transaction on all the RAC nodes for a table being captured. As an alternative a dummy table can be added
to the extract parameter file and doing DML on this table from all the threads would give extract commit boundary current checkpoints for all the threads
D) Once said message is detected, Stop the extract, perform dblogin, and alter for conversion to Integrated as shown below
4.
Connect to the Extract database, and grant the following priviege to GG Admin user
SQL>exec dbms_goldengate_auth.grant_admin_privilege('OGG_TS');
Login into GGSCI?Check to see if upgrade possible
GGSCI> DBLOGIN USERID <ID> PASSWORD <PW>
GGSCI> INFO <extract_name> UPGRADE
Upgrade may fail, in case of existing open transactions
GGSCI>stop extract <extract_name>
GGSCI>dblogin userid <ggadmin>,password <password>
--Register the extract in the database if not done already
GGSCI>register extract <extract_name> database
GGSCI>alter extract <extract_name>,upgrade integrated tranlog
GGSCI>start extract <extract_name>
相关文章推荐
- ogg由普通模式转换成集成捕捉模式实验
- 【翻译自mos文章】OGG的集成捕捉模式支持Oracle database标准版么?
- ogg 有集成捕捉模式转换为普通模式
- 【翻译自mos文章】OGG的集成捕捉模式支持Oracle database标准版么?
- ogg在oracle database 11.2.0.3上还是谨慎使用集成捕捉模式
- [翻译自MOS文章]在OGG的trail文件中始终包括lob类型记录的方法
- 【翻译自mos文章】怎么检查Oracle GoldenGate(OGG)的checkpoint file 是否被locked?
- android usb otg模式转换成host模式(不使用otg线连接,只用普通usb四线连接)
- [翻译自MOS文章]怎么在OGG 12c版本中把replicat进程重新定位到之前的trail文件位置上?
- 一篇能很好反映普通接口多态 工厂模式 依赖注入三者的耦合强度区别的文章
- 【翻译自mos文章】OGG Director 不会purge log table
- 【翻译自mos文章】OGG add Supplemental Logging 时失败,报错为 块损坏(Block Corruption)
- 【翻译自mos文章】OGG的Director界面 显示mgr进程是红色的叉号,其实mgr是up的状态
- 【翻译自mos文章】Main Note - ogg的 Supplemental Logging and TRANDATA
- 【翻译自mos文章】OGG支持oracle db 11g中的不可见索引吗?
- 【翻译自mos文章】在OGG (Oracle GoldenGate) 中使用SCHEMATRANDATA的话,需要额外的db patch
- XML内嵌架构模式转换为普通数据文件
- [翻译自MOS文章]OGG的管理者进程总是监听在默认主机和端口上.
- 【翻译自mos文章】Oracle GoldenGate(OGG) trail file的最大大小
- 【翻译自mos文章】当在Windows 2008 server 上安装OGG Director Server之后,Director Web无法访问