When restarting the MINE process, there will be some additional internal work required by the MINE process to ensure all changes are captured and there are no gaps in the replication. This work is done automatically on startup by the MINE process.
...
The APPLY process is not impacted when there is a restart on the MINE process. If it already has a PLOG delivered, it will not ask MINE for the new copy. It knows that SCN of last applied transaction and can carry on from the last applied SCN.
When restarting MINE, the Dbvisit Replicate console will initially report what appears to be incorrect progress counters:
| No Format | ||
|---|---|---|
| ||
-MINE IS running. Currently at plog 66 (redo sequence 1424 [1] 1831 [2]) and SCN 47476178 (1206/1301/20152016 18:57:13). APPLY IS running. Currently at plog 52 and SCN ... (1206/1301/20152016 10:38:48). Progress of replication orcl:MINE->APPLY: total/this execution -------------------------------------------------------------------------------------------------------------------------------------------- SCOTT.AVI_OBJECTS: 133% Mine:6000/6000 Unrecov:0/0 Applied:8000/0 Conflicts:0/0 Last:--/-- -------------------------------------------------------------------------------------------------------------------------------------------- |
...
| No Format | ||
|---|---|---|
| ||
dbvrep> list obsolete redo
Thread 1 last obsolete sequence#: 20606 (7 hours and 6 minutes ago) |
Starting in Replicate 2.8 extra information is displayed regarding how far back the process will go when it is started.
| No Format | ||
|---|---|---|
| ||
dbvrep> shutdown all Upon restart MINE will go back to redolog 5901 (thread 1), going back 4 logs. Upon restart APPLY will go back to plog 5901, going back 4 plogs. Are you sure you want to shutdown? (Yes/No) [No] yes Dbvisit Replicate MINE process shutting down. |
The initialization is not required when MINE process has been paused. Only when the MINE process has been restarted.
...