mos文章将ogg捕捉模式由普通模式转换成集成捕捉
来源:互联网 发布:云技术与大数据 编辑:程序博客网 时间:2024/05/22 02:24
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>
阅读全文
0 0
- mos文章将ogg捕捉模式由普通模式转换成集成捕捉
- ogg由普通模式转换成集成捕捉模式实验
- ogg 有集成捕捉模式转换为普通模式
- 【翻译自mos文章】OGG的集成捕捉模式支持Oracle database标准版么?
- ogg在oracle database 11.2.0.3上还是谨慎使用集成捕捉模式
- STM32的定时器--输入捕捉模式
- AutoCAD系统变量: OSMODE --设置“对象捕捉”的运行模式
- webpy开发笔记01-调试模式下异常捕捉问题
- AutoCAD系统变量: OSMODE --设置“对象捕捉”的运行模式
- 小熊STM32学习总结:STM32的定时器--输入捕捉模式
- PHP捕捉普通异常和致命错误
- 如何将应用程序由“调试”模式调成“部署”模式?
- 6. avr定时器/计数器1 --TC1 --输入捕捉模式 (捕获外部事件模式)
- 规则引擎需求(捕捉业务规则需求,将需求转换为规则引擎)
- 规则引擎需求(捕捉业务规则需求,将需求转换为规则引擎)
- 【翻译自mos文章】OGG Director 不会purge log table
- 将16:9的横屏PPT转换为4:3普通模式
- 如何在arcmap10.0以及以上版本中使用arcgis9.X系列的编辑捕捉模式
- 创建一个不显示窗口的Win32程序
- mkdir命令
- 严重 A child container failed during start——Caused by: java.lang.NoClassDefFoundError: org/springframe
- SpringMVC后台实现跨域支持
- 71 linux usb设备驱动
- mos文章将ogg捕捉模式由普通模式转换成集成捕捉
- keepalived+lvs无法访问vip或访问超时
- Qt下将文件输出为图片文件
- java实现pdf的生成下载打印,java生成pdf电子账单,java生成pdf合同模板
- QT打印到控制台
- jsp页面定义公共变量及项目根目录获取方式
- php.ini修改php上传文件大小限制的方法详解
- android之服务service远程服务
- 【笔记】IPV6地址格式