ORA-16170: Terminal recovery may have left the database in
an inconsistent state
- 1 Answers
- 2305 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-12491: DBHIGH value does not dominate DBLOW
PLS-00720: type 'string' has evolved
ORA-28239: no key provided
ORA-00202: controlfile: 'string'
ORA-36679: (XSDPART17) workspace object contains a leaf (workspace object) that is not part of the partition dimension workspace object.
ORA-06975: X.25 Driver: connect to host failed
ORA-33078: (XSAGDNGL39) In AGGMAP workspace object, the hierarchy dimension QDR workspace object must refer to a dimension.
ORA-00444: background process "string" failed while starting
ORA-13045: invalid compatibility flag
ORA-00307: requested INSTANCE_NUMBER out of range, maximum is string
ORA-07665: ssrexhd: recursive exception encountered string string string string string string
ORA-07635: smsdbp: $SETPRT failure
Oracle Errors 
