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
- 2998 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 |
ORA-01521: error in adding data files
NNL-01069: Log file name: string
NNL-00220: Statistic counter logging is currently disabled
SQL*Loader-00488: %s not a named collection type for filler field string
ORA-32627: illegal pattern in MODEL FOR LIKE loop
O2U-00201: Illegal arguments to function o2upt()
TNS-00527: Protocol Adapter not loadable
TNS-00293: Trace File Name : string
ORA-12716: Cannot ALTER DATABASE CHARACTER SET when CLOB data exists
ORA-01162: block size string in file header does not match configured block sizes
ORA-29301: wrong DBMS_PITR package function/procedure order
PCC-02370: An EXEC TOOLS MESSAGE host variable is not type char
Oracle Errors 
