ORA-16170: Terminal recovery may have left the database in
an inconsistent state
- 1 Answers
- 2422 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 |
RMAN-06498: skipping datafile string; already backed up string time(s)
ORA-00279: change string generated at string needed for thread string
ORA-24411: Session pool already exists.
ORA-31418: source schema string does not exist
ORA-38424: no attribute set currently assigned to the expression set
ORA-28166: duplicate rolename in list
ORA-07204: sltln: name translation failed due to lack of output buffer space.
RMAN-08535: channel string: looking for autobackup on day: string
RMAN-10003: unable to connect to target database
ORA-24781: branches don't belong to the same global transaction
TNS-00219: Pump Strategy : string
NNO-00119: line string: server not authoritative for name "string", data ignored
Oracle Errors 
