When restarting the Mine MINE process, there will be some additional internal work required by the Mine process 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 processMINE process.
To ensure complete transactional integrity, the Mine process MINE process will have to go back to the last uncommited SCN for a transaction and start parsing for any changes since that SCN. There may have been a future commit for that transaction and Mine needs MINE needs to ensure that all the changes have been mined. This may mean that Dbvisit Replicate will go to the archive redo logs to capture the full transaction history. Plogs are written again on Mine restartsMINE restarts.
The Apply process is not impacted when there is a restart on the Mine processMINE process. If it already has a plog delivered, it will not ask mine for MINE for the new copy. It knows that SCN of last applied transaction and can carry on from the last applied SCN.
When restarting MineMINE, the Dbvisit Replicate console will initially report what appears to be incorrect progress counters:
...
The Apply SCN is set to 0 while the Mine process MINE process goes back to the last uncommitted SCN. The % progress will also not reflect the true number while this initialization is carried out.
...
To find out how far back the Mine process MINE process will go on a restart, run the following command. This lists the last redo log no longer required by the Mine processMINE process:
| No Format | ||
|---|---|---|
| ||
dbvrep> list obsolete redo Thread 1 last obsolete sequence#: 20606 (7 hours and 6 minutes ago) |
...
The initialization is not required when Mine process MINE process has been paused. Only when the Mine process MINE process has been restarted.