Goldengate:ERROR 180 encountered commit SCN that is not greater than the highest SCN already processed

How to recover from Extract ERROR 180 encountered commit SCN that is not greater than the highest SCN already processed

This is the summary of Metalink Doc:987379.1

This error occurs in an Oracle RAC environment after a transaction is written to the idle node but does not yet appear in the redo log when the current transaction is processed. This transaction will have a higher SCN then the previous transaction 
In order to avoid to live this problem the steps in (Encountered SCN That Is Not Greater Than The Highest SCN Already Processed ) articale must be done 

But If you have encountered this problem here is the solution 
Do an ETROLLOVER on Extract, and take note of the new sequence number of the trail file. 
ALTER EXTRACT [name], ETROLLOVER
Start extract 
START EXTRACT [name]
Send PUMP, LOGEND, to see if it's at the end of the previous trail. 
SEND EXTRACT [pump_name], LOGEND
Once it is at the end of the trail file, You must stop the pump, and do an ETROLLOVER for it too. Take note of the new trail file sequence number that is created from this step
STOP EXTRACT [pump_name] 
ALTER EXTRACT [pump_name], ETROLLOVER
Alter the pump to SEQNO to the new trail file created from step #1. 
ALTER EXTRACT [pump_name], EXTSEQNO ##### EXTRBA 0
Restart pump 
START EXTRACT [pump_name]
Send Replicat, LOGEND to make sure it has processed all the remaining data, and stop Replicat. 
SEND REPLICAT [name], LOGEND 
STOP REPLICAT [name]
If replicat is not at end of trail, generate a report and forcestop replicat
SEND REPLICAT [name], REPORT
STOP REPLICAT [name]!
Add the following parameters to replicat parameter file to allow replicat to process each trail record as a single transaction, or set them to 1 if you have any of these parameters
GROUPTRANSOPS 1
MAXTRANSOPS 1
Restart replicat
START REPLICAT [name]
Once replicat has completely processed the trail, stop the replicat
STOP REPLICAT [name]
Edit the replicat parameter file: 
Add parameter HANDLECOLLISIONS to Replicat parameter file 
Remove or comment out GROUPTRANSOPS and MAXTRANSOPS or revert them back to their original values.
ALTER REPLICAT, SEQNO to the new trail file created in step #4. 
ALTER REPLICAT [name], EXTSEQNO ###### EXTRBA 0
Start Replicat
START REPLICAT [name]
Once Replicat has processed the out of order SCN operations, disable HANDLECOLLISIONS. You could also look for the CSN and wait for Replicat to checkpoint past it.
SEND REPLICAT [name], NOHANDLECOLLISIONS
Edit the replicat parameter and comment out the HANDLECOLLISIONS parameter. You do not need to stop/restart replicat. This will ensure that on any subsequent replicat restarts the parameter is disabled

时间: 2024-10-23 10:26:52

Goldengate:ERROR 180 encountered commit SCN that is not greater than the highest SCN already processed的相关文章

IMP-00003: ORACLE error 3113 encountered ORA-03113: end-of-file on communication channel

 IMP-00003: ORACLE error 3113 encountered  ORA-03113: end-of-file on communication channel . . importing table    "SFP_FILE_6"      11179 rows imported IMP-00017: following statement failed with ORACLE error 3113:  "DECLARE  SREC DBMS_STATS

EXP-00008: ORACLE error 904 encountered的解决方法

error|oracle|解决 [错误情况] [oracle@ccdevsvr admin]$ exp wmap/pass@jackeydb Export: Release 8.1.7.4.0 - Production on Fri Oct 8 11:28:37 2004 (c) Copyright 2000 Oracle Corporation.  All rights reserved. Connected to: Oracle9i Release 9.2.0.1.0 - Productio

An error was encountered while running(Domain=LaunchSerivcesError, Code=0)

今天突然遇到这样一个错误,编译可以通过,但是运行就会弹出这个错误提示: An error was encountered while running(Domain=LaunchSerivcesError, Code=0) 解决办法就是重置模拟器. 点击模拟器菜单中的Reset Contents and Settings,完成后,再运行就OK了!

Oracle数据库的SCN转换成时间和时间转换成SCN

Scn转换成时间: select to_char(scn_to_timestamp(3998591352171),'YYYY-MM-DD HH24:MI:SS') from dual:   时间转换成scn: select timestamp_to_scn(to_date('2011-04-14 11:10:25','YYYY-MM-DD HH24:MI:SS')) from dual

Goldengate OGG常见问题与错误列表

 Goldengate OGG常见问题与错误列表  以下列出了OGG一些常见的问题与错误及其解答:   Note: 966211.1 How To Resync A Single Table With Minimum Impact To Other Tables' Replication? Note: 966227.1 Troubleshooting TCP/IP Errors In Open Systems Note: 972954.1 What Causes The 'Bad Column

【OGG】OGG故障错误处理总结

[OGG]OGG故障错误处理总结 第一章 GoldenGate错误分析与处理 在维护GoldenGate过程中,由于各种意外情况,难免还是会遇到各种各样的问题.掌握一些常见的GoldenGate故障诊断和错误分析的方法是非常有必要的,而且掌握这些错误分析工具也进一步加深对GoldenGate产品的认识与对GoldenGate原理的理解.   1.1   GoldenGate常见异常处理 GoldenGate运行起来后,随着时间的推移可能会碰到各种各样的问题,下面就来介绍常见的异常现象以及常见的异

oracle中scn号是commit之后产生的,还是commit之前产生的?

问题描述 oracle中scn号是commit之后产生的,还是commit之前产生的? 如果是commit之后产生的,那么在commit之前scn都没有,还怎么用比较scn号大小的方法来实现读一致性呢? 假设scn号是在commit之后产生的,在判断读一致性时是根据scn号的大小去控制的,比如事务开始时最大的scn号是1000,当读到此事务开始之后有人修改过但未提交的数据时,比如这次修改的scn是1001,系统一看比事务开始时最大的scn号1000还大,就直接去undo中读取被修改之前的数据来保

goldengate–使用filter+@GETENV在线重新初始化指定的table

goldengate–使用filter+@GETENV在线重新初始化指定的table 转载:http://www.easyora.net/blog/using_filter_getenv_function_to_initialize_special_table.html         在oracle-oracle goldengate的复制环境中,有时候会碰到一些紧急的问题一时无法修复,为了避免影响整个复制环境的复制进度,采取跳过错误事务或者跳过特定对象的办法使得goldengate继续同步:

Oracle利用scn增量备份实现数据库增量恢复

使用rman基于scn实现数据库增量恢复是在dg中修复gap的时候常见的方法,其实该方法也可以使用常规的增量恢复,通过人工控制,实现数据库的某种特殊的业务需求(特殊的数据迁移).处理思路主要是获得备库的数据文件最小scn(这个scn可能是通过全备恢复或者增量恢复产生),然后基于该SCN实现数据库增量备份,然后利用该备份进行增量恢复. 数据库版本  代码如下 复制代码 SQL> select * from v$version;   BANNER --------------------------