Reconcile command fails. Is it possible to run it again?
There are a number of situations where the reconcile errors out or does not act as intended. Some of the common ones include:
a. Issuing reconcile on target sp_ctrl when the Post queue has not yet spawned.
b. Issuing reconcile on wrong queue name or specifying the servername when a named post queue exists.
c. Specifying wrong SID name in the config file or in the reconcile command.
d. Running reconcile on a Post queue when the Post process is running.
e. Running reconcile on source.
f. Reconciling up to wrong log sequence # or SCN #.
Except for the last one, the others are purely a syntax issue or a procedural issue and reconcile simply errors out without doing anything. The command can be re-issued once the syntax or other procedural errors are corrected. The last one, where the user reconciled up to the wrong sequence # or SCN #, needs to be dealt with special care if the situation is to be salvaged. For example if one recovered or intend to recover the target database up to log sequence # 10 but instead reconciled up to log sequence # 20, then one has two options to correct the mistake:
1. Run the whole process of hotbackup with reconcile once again.
2. If one has not yet opened the target database, then one can keep recovering the database up to log sequence # 20. This will save time and effort.
The logic behind the workaround in paragraph 2 is as follows. When one mistakenly reconciled up to log sequence # 20, one removed all the messages in queue up to archive log # 20. Since the target had initially been recovered up to log sequence # 10, the target will be out of sync with source (data from log 10 -20 will be missing). However, if the target is not yet opened, one can still salvage the situation by recovering the target up to log sequence # 20. By the same token, if one ran reconcile up to log sequence # 5 whereas the target was recovered up to log sequence # 10, one can run the reconcile once again and specify the log sequence # 10 this time.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center