How to re-synch primary and standby database?
555329Aug 18 2008 — edited Aug 18 2008Hello everyone,
Working on 10g R2/windows server 2003, I have configured a physical standby database but, I have an issue, and don't know how to resolve it.
We were making an update that made some DDL and DML on our application, and for security reason we
1. we ensure that primary and standby are in sync
2. We made a cold backup of the primary database
3. We Deferred the redo shipping between primary and standby
4. We applied changes on primary database
But the big issue is that, for any reason my colleague did the following.
a) made above steps 1,2,3,4
b) after the update he kept the resulted archived log files generated during to another location
c) He restore the cold backup before the update(step 2 above)
c) he applied again the update.
Now the issue is
At the first update step(2), the sequence# 553 was applied to the stand by before the update
At the second update step(c) above another sequence# 553 was created but stored localy in the primary database, because the both servers were deverged (step 3 above).
Technically both servers cannot be in sync again,because sequence# 553 at the first update has next_change# 80307804 and sequenc# 553 at the second update has next_change# 80461356.
Question:
How Can I do to rollback the the first sequence# 553 ( before the first update) on the standby database? in order to apply the sequence#553 generated at the second update and then re-sync both servers to roll forward subsequent sequence#? 554,etc...
Thank you for your help