ORA-16170: Terminal recovery may have left the database in
an inconsistent state
- 1 Answers
- 2425 Views
- I also Faced
- E-Mail Answers
Answer Posted / 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 |
Post New Answer View All Answers
ORA-26027: unique index string.string partition string initially in unusable state
ORA-16626: failed to enable specified object
ORA-26029: index string.string partition string initially in unusable state
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
if the lengths of two wires are same and the area of cross sections is 4:7 then what will be the ratio of current passing through these wires
ORA-16627: No standby databases support the overall protection mode.
NZE-28890: Entrust Login Failed
RMAN-05017: no copy of datafile number found to recover
ORA-26084: direct path context already finished
when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly
When i am connect database through toad,one error occured. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. plz help me thanks advance.............
ORA-26082: load of overlapping segments on table string.string is not allowed
How to resolve QSM-01108 error. I have no OR conditions in my query, but do have 9 IN conditions. The error says the max limit is 2 while I have 257 number of disjuncts. However, if I remove even a single IN condition, the query is rewritten. I cannot change my query. How can I resolve this issue?
IMG-02003: 2FF03 - incorrect color histogram feature specification
ORA-26028: index string.string initially in unusable state
