Chinaunix首页 | 论坛 | 博客
  • 博客访问: 360857
  • 博文数量: 86
  • 博客积分: 1460
  • 博客等级: 上尉
  • 技术积分: 848
  • 用 户 组: 普通用户
  • 注册时间: 2009-07-12 14:07
文章分类

全部博文(86)

文章存档

2017年(36)

2016年(17)

2015年(1)

2013年(12)

2012年(2)

2011年(1)

2010年(1)

2009年(16)

我的朋友

分类: LINUX

2016-06-09 16:29:17

goldengate 迁移通过设置Extract  extseqno  extrba 方式,报错
解决需要通过设置begin  时间的方式,才可以,但是info extract group_name showch 显示的时间没有精确到毫秒,通过设置时间可能会导致重复抽取,R进程会重复应用,需要目标表有主键控制,通过设置handlecollisions  让ogg 自己解决冲突问题,或者最好在业务低峰期操作。

goldengate 版本12C  12.1.0.1.0

请参考
Extract Abends with OGG-01028 Non-Standard Redo Detected in 10g Compatible Format (文档 ID 1313864.1)

Applies to:

Oracle GoldenGate - Version 10.4.0.19 and later
Information in this document applies to any platform.
Checked for relevance 15-Oct-2012

Symptoms

OGG Extract abends : Non-Standard Redo Detected in 10g compatible Format

Cause

Cause 1
This error occurs when  the extract's starting seqno# and rba are not on log write boundary. When positioning by time, extract will find the right log write boundary by itself.

Cause 2
Extract may fail with same error due to bug in AsyncReader logic. This issue occurs when the AsyncReader reaches an EOF condition and stops read operations before the REDO thread detects the EOF condition and instructs the AsyncReader thread to stop reading.

Cause 3
Extract is altered by extseqno and extrba
alter extract EACHINTP thread 1, extseqno 10552,extrba 26465408
alter extract EACHINTP thread 2, extseqno 5431,extrba 1148456

Cause 4
Extract with DBLOGREADER can produce this error reading Oracle database versions that support DBLOGREADER APIs and is related to the premature logfile switching, hence "bad" data has been read by the DBLOGREADER api and passed to GoldenGate Extract, which has caused the Extract abend. A restart does not resolve this issue. Please refer to the reference manual for Oracle database versions that support DBLOGREADER APIs.

 

 

Solution

Solution 1
Alter extract to position by timestamp and restart

ggsci> ALTER EXTRACT {extract group}, BEGIN {timestamp}
ggsci> START {extract group}

Solution 2
1. This issue is recoverable by restarting extract
2. This issue can be avoided via 'tranlogoptions _NOREADAHEAD CURRENT'
3. Upgrade to 11.2.1.0.0 or later

Solution 3
Alter extract to position by timestamp and restart

ggsci> ALTER EXTRACT {extract group}, BEGIN {timestamp}
ggsci> START {extract group}

Solution 4
Include parameter
You need to upgrade to v11.2.1.0.26 or later and specify this parameter
TRANLOGOPTIONS _DISABLESTREAMLINEDDBLOGREADER
As of version 12 this option is permanently disabled.

阅读(3679) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~