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 |
ORA-39025: jobs of type string are not restartable
ORA-12415: A column of another datatype exists on the specified table
PLS-00582: attribute declarations are not allowed in opaque types
ORA-16771: Converting physical standby to primary failed in the failover operation.
ORA-19583: conversation terminated due to error
ORA-14069: invalid TABLESPACE_NUMBER value
KUP-03016: length specified for FIXED records must be greater than 0
ORA-01910: TABLES keyword expected
ORA-13430: the GeoRaster object has null attribute(s)
PCC-00002: Invalid syntax at column number in line number of file string
ORA-16227: DDL skipped due to missing object
RMAN-06076: datafile string contains wrong datafile