Resynchronizing an out-of-sync table - Oracle Golden Gate

 In this procedure, there are two Replicat groups:


● The original group, known as group A

● A new group that you will create, known as group B


To resynchronize a table

1. Comment out the out-of-sync table in the original Replicat parameter file.


2. Stop the original Replicat and start it again so it continues processing the tables that are not out-of-sync.


STOP REPLICAT <groupA>

START REPLICAT <groupA>


3.Write down the timestamp on the source system.


4.Try to resolve any long-running transactions on the source out-of-sync table. You will be copying the source data to the target, and if transactions are open while the copy is being made, they will not be captured.


5. Start a copy of the source data.


6. Import the copy to the target table.


7. Create a new Replicat group for the out-of-sync table, using BEGIN to start at the source timestamp that you recorded step 3, and using the existing trail for EXTTRAIL.


ADD REPLICAT <groupB>, EXTTRAIL <existing trail>,BEGIN <yyyy-mm-dd hh:mm:ss>


8. Create a parameter file for the new group and include HANDLECOLLISIONS.

EDIT PARAMS <groupB>


9.Start the new Replicat group. START REPLICAT <groupB>


10. View the lag of the new group until it shows “At EOF, no more records to process.”

SEND REPLICAT <groupB>, GETLAG


11. Stop the new Replicat group.STOP REPLICAT <groupB>


12. Edit the parameter file of the new group to comment out or remove HANDLECOLLISIONS.


13. Start the new Replicat group.


START REPLICAT <groupB>


The next steps merge the table back with the others so that only one Replicat group is needed again.


14. Stop Extract. STOP EXTRACT <extract_group>


15. View the lag of each Replic at group until it shows “At EOF, no more records to process.”


SEND REPLICAT <groupA>, GETLAG

SEND REPLICAT <groupB>, GETLAG


16. Stop both Replicat groups.


STOP REPLICAT <groupA>

STOP REPLICAT <groupB>


17. Uncomment the newly synchronized table in the original Replicat parameter file.


18. Start Extract.


START EXTRACT <extract_group>


19. Start the original Replicat.


START REPLICAT <groupA>


20. Delete the new Replicat that you created.


DELETE REPLICAT <groupB>


Note : we can use find current_scn from source database and take export using the flashback parameter and copy the tables to target, while starting dummy replicat group we use start replicat after csn.


Comments

Post a Comment

Popular posts from this blog

How to Solve - "WAIT FOR EMON PROCESS NTFNS"

Event Monitor Process in short called as EMON is generally used by oracle to send notification. Often applications uses Database Change Notification process also called as DBCN to be aware of changes in the database, based on these notifications they take further actions. Often clients subscribe to the database and notifications are send as callback to them. In some cases you will notice database sessions are showing wait event "WAIT FOR EMON PROCESS NTFNS" and it can even make your database un-responsive. One observation can be these processes are taking more CPU (may not in be in all cases). As stated EMON process deals with database notification and it's spawn and gets down itself and Administrators have no control on theses processes. Anyone can go through oracle documents to read more EMON functioning process.  EMON uses oracle advanced queues and database queue notifications into them and EMON process these notifications to clients based on their subscriptions. In s...
Read more

Query Regression - "OR" Transformation Oracle 19c

Recently while upgrading Oracle Database from version 12.1 to 19.10 found there were couple of queries which was running slow post upgrade. Usually these type of behavior is seen while upgrading to newer version and oracle provide various ways to fix them. The difference between good and bad plan was an introduction of  "MERGE JOIN CARTESIAN" (aka MJC) and that's in where regressed query in 19c taking most of the time. MJC sometimes works for queries but in this case it was clearly not helping.  We had following options here:     1. Copy the profile from 12c to 19c database and it worked, but the problem was not just to specific query but with many similar query. This means profile option is not very attractive in this case.     2. We also tried running query with OFE 12.1 to use the same optimizer features as previous version and query behaves well. Though this option can't be placed as we need to use 19c OFE and can be placed only for testing purpose. ...
Read more

Error Processing Request. - Oracle APEX Post upgrade (Invalid WWV_FLOW_SESSION_RAS)

There would be occasions where you would upgrade your oracle database which is hosting your APEX and post upgrade you get error while opening APEX URL " Error Processing Request Contact your application administrator " This looks very strange as you have just upgraded only database. Database version and APEX version are compatible. For Argument lets say both are on 19c.  Now since UI doesn't give detailed information about the error you would need to get to backend oracle database and query view apex_debug_messages.     select * from apex_debug_messages; Looking at the results of this view you would get the clue of the error in this case it was:      ORA-04063 package body APEX_190100.WWV_FLOW_SESSION_RAS has error This means this package body has problem and looking at the status of this body it's found to be invalid and when you try to compile it get following error      alter package APEX_050100.WWV_FLOW_SESSION_RAS compile body;  ...
Read more