ORA-16170: Terminal recovery may have left the database in
an inconsistent state
- 1 Answers
- 2320 Views
- I also Faced
- E-Mail Answers
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 |
ORA-09772: osnpmetbrkmsg: message from host had incorrect message type
ORA-19321: Could not open HTTP connection to host (string): port (string)
ORA-07390: sftopn: translate error, unable to translate file name.
ORA-31423: change table string does not contain column string
ORA-29532: Java call terminated by uncaught Java exception: string
ORA-00107: failed to connect to ORACLE listener process
ORA-24185: Transformation string.string, does not exist
TNS-00286: Max Connect Time (secs) : number
PCB-00637: Host variable is not an exact binary integer
ORA-00962: too many group-by / order-by expressions
LPX-00123: duplicate ID "~S"
NNL-00919: Time until server shutdown: string
Oracle Errors 
