ORA-16170: Terminal recovery may have left the database in
an inconsistent state
Answer / guest
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.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
TNS-12668: Dedicated server: outbound protocol does not support proxies
ORA-07741: slemop: $OPEN failure
TNS-03508: Failed to create address string
RMAN-10024: error setting up for rpc polling
ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
ORA-02882: sou2o: Could not register SGA for protection
PLS-00302: component 'string' must be declared
ORA-06006: NETASY: dialogue execute failure
NNL-00231: Controller NOCONFIRM mode is now string
SQL-02120: First and second arguments to SQLRCN both null
ORA-28118: policy group already exists
ORA-09771: osnmwrtbrkmsg: bad return code from msg_send.