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-06259: NETNTT: cannot read from remote process
ORA-25238: too many recipients specified for message destination string
NNL-00831: Deletes refused, name is not a leaf name: number
ORA-22896: cannot have both scope and referential constraint on REF column "string"
RMAN-06132: cannot backup datafile string because it is not in the controlfile
ORA-30508: client logon triggers cannot have BEFORE type
ORA-04061: existing state of string has been invalidated
ORA-19321: Could not open HTTP connection to host (string): port (string)
ORA-00221: error on write to controlfile
ORA-16596: object not part of the Data Guard broker configuration
ORA-06005: NETASY: dialogue file read failure
DRG-50929: parser internal on line string on column string