Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16170: Terminal recovery may have left the database in
an inconsistent state
- 1 Answers
- 2994 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 |
NNL-00853: Renames refused, new name already exists: number
ORA-16557: The database is already in use.
RMAN-08150: created global script string
ORA-12488: maximum label does not dominate minimum label
ORA-02761: File number to be canceled is negative.
ORA-13373: element of type extent is not supported for geodetic data
ORA-14130: UNIQUE constraints mismatch in ALTER TABLE EXCHANGE PARTITION
TNS-01177: Log Status is OFF. Log file/directory unchanged
ORA-03287: invalid FREELIST GROUP specified
ORA-24306: bad buffer for piece
DRG-10752: DEFAULT_INDEX_MEMORY cannot be greater than MAX_INDEX_MEMORY
ORA-26099: direct path context is already prepared
Oracle Errors 
