ORA-16170
Terminal recovery may have left the database in an inconsistent state
Cause
When terminal recovery is invoked in a standby database without synchronous log shipping, in the rare case of the recovery session being in an unrecoverable state, terminal recovery cannot bring the standby database to a consistent SCN boundary if the primary database continues to have redo thread(s) open.
Action
Continue standby recovery with additional log shipping from primary.
ORA-16170
Terminal recovery may have left the database in an inconsistent state
Cause
When terminal recovery is invoked in a standby database without synchronous log shipping, in the rare case of the recovery session being in an unrecoverable state, terminal recovery cannot bring the standby database to a consistent SCN boundary if the primary database continues to have redo thread(s) open.
Action
Continue standby recovery with additional log shipping from primary.
ORA-16170
Terminal recovery may have left the database in an inconsistent state
Cause
When terminal recovery is invoked in a standby database without synchronous log shipping, in the rare case of the recovery session being in an unrecoverable state, terminal recovery cannot bring the standby database to a consistent SCN boundary if the primary database continues to have redo thread(s) open.
Action
Continue standby recovery with additional log shipping from primary.
