ORA-16170: Terminal recovery may have left the database in
an inconsistent state
- 1 Answers
- 2290 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-31010: XML element index string exceeds maximum insertion index string
ORA-35282: (SNSYN166) The format of the AGGREGATE function is: AGGREGATE(varname USING aggmap-name [COUNTVAR intvar-name] [FORCECALC])
NNO-00269: configuration database is version string, server requires at least version string
NZE-29178: certificate serial number is in CRL
ORA-12843: pdml lock not held properly on the table
ORA-30451: internal error
ORA-38601: FI Not enough memory for frequent itemset counting: string
ORA-07657: slsprom:$ASSIGN failure
ORA-26664: cannot create STREAMS process string
ORA-29322: SCN string size too long -- maximum size 58 bytes/characters
ORA-02213: duplicate PCTUSED option specification
ORA-19629: no files in specified archivelog SCN range
Oracle Errors 
