This article provides a solution when MINE does not update the PLOG sequence to the latest one after restart.
Re-starting MINE goes back to OLD PLOGS
Applicable Error Code
dbvrep> shutdown mine
Upon restart MINE will go back to redolog 106421 (thread 1), going back 5,028 logs
Replicate Version 2.8
Sometimes when we restart MINE due to scheduled maintenance of server or database , the MINE goes back to very OLD plog sequence instead of latest ones.
The list transactions from the console too does not show any old transactions in the database and shows only current transactions.
The list obsolete redo shows from where the MINE process would start processing after restart(It is a good practice to run this before a MINE shutdown) .
The workaround was to manually set the MINE to the PLOG sequence from where it would start processing.
To resolve the issue set then below parameter and re-start the MINE process.
dbvrep> set _MINE_RETIRE_OBSOLETE_TRANSACTIONS =YES
After the restart MINE started to process correctly for future restarts.