...
| No Format |
|---|
SQL> select REDO_THREAD,REDO_SEQUENCE,PLOG_SEQUENCE from DBRSMINE_RLOG_PLOG_MAP where PLOG_SEQUENCE=1056;
REDO_THREAD REDO_SEQUENCE PLOG_SEQUENCE
----------- ------------- -------------
1 1056 1056 |
...
| Note |
|---|
When fetcher is used, you don't have to bring down the fetcher and you need not delete archives from mine_stage. The mine would automatically pick up the first archivelog from the mine_stage directory to generate the required PLOG and then move forward. |
| Note |
|---|
You can set plog sequence (in this example 1056) to the most recent uncorrupted plog. Usually this sequence should be equal to the plog sequence APPLY was processing before shutdown. But if you are not sure you can always set it 2-3 sequences behind the actual APPLY plog. There is no issue with this. Replicate is aware of the changes that have already been applied to the target and will not try to re-apply them. However, it will have to read through any previously applied plogs to determine this, and that may take some time, depending on the size of the plogs and the data contained within. Generally speaking there is usually no reason to set the sequence too far in the past. Whatever plog sequence you choose you need to ensure that the corresponding archlogs exist. MINE will re-mine all plogs from and including sequence you specified and APPLY will process all plogs from and including this sequence. |