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

Source: Internet
Author: User

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 etrolover on extract, and take note of the new sequence number of the trail file.
Alter extract [name], etrolover
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 etrolover 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], etrolover
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 cocould 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

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.