OCI-16425
a RECOVER FINISH failed because recovery incarnation string is not the target incarnation string
Cause
RECOVER FINISH failed because a new incarnation existed on the physical standby database. This situation could happen if two failures occurred in a short time and the current failover target was still in the previous incarnation.
Action
Issue real-time apply recovery and see if recovery can proceed on the new branch by checking if logs on the new branch are applied by recovery. If so, issue another RECOVER FINISH. Otherwise, issue ALTER DATABASE ACTIVATE STANDBY DATABASE.
OCI-16425
RECOVER FINISH cannot be issued when recovery branch string is not the target branch string.
Cause
RECOVER FINISH failed because a new branch existed on the physical standby database.
Action
Issue real-time apply recovery and see if recovery can proceed on the new branch by checking if logs on the new branch are applied by recovery. If so, issue another RECOVER FINISH. Otherwise, issue ALTER DATABASE ACTIVATE STANDBY DATABASE.
OCI-16425
RECOVER FINISH cannot be issued when recovery branch string is not the target branch string.
Cause
RECOVER FINISH failed because a new branch existed on the physical standby database.
Action
Issue real-time apply recovery and see if recovery can proceed on the new branch by checking if logs on the new branch are applied by recovery. If so, issue another RECOVER FINISH. Otherwise, issue ALTER DATABASE ACTIVATE STANDBY DATABASE.
