ORA-16199: Terminal recovery failed to recover to a consistent point

Cause : See alert log for more details

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Try to resolve the problem. Retry terminal recovery. If the problem occurs repeatedly and cannot be resolved, call Oracle support.

update : 30-04-2017

ORA-16199 - Terminal recovery failed to recover to a consistent point
ORA-16199 - Terminal recovery failed to recover to a consistent point

  • ora-12641 : Authentication service failed to initialize
  • ora-00109 : invalid value for attribute string: string
  • ora-25235 : fetched all messages in current transaction
  • ora-12226 : TNS:operating system resource quota exceeded
  • ora-12665 : NLS string open failed
  • ora-30575 : ConText Option not installed
  • ora-12612 : TNS:connection is busy
  • ora-14187 : partitioning method for LOCAL index is inconsistent with that of the underlying table
  • ora-27367 : program "string.string" associated with this job is disabled
  • ora-25307 : Enqueue rate too high, flow control enabled
  • ora-39213 : Metadata processing is not available
  • ora-13835 : invalid attribute name specified
  • ora-32502 : Cannot execute command. Flash Freeze is not in effect
  • ora-38853 : cannot mark instance string (redo thread string) as disabled
  • ora-39956 : duplicate setting for PL/SQL compiler parameter string
  • ora-31695 : Inconsistent master table on restart. The following SQL statement returned string identical objects. string
  • ora-01168 : physical block size string does not match size string of other members
  • ora-33334 : (DSSEXIST04) Analytic workspace string is not attached.
  • ora-02039 : bind by value is not allowed for array type
  • ora-28551 : pass-through SQL: SQL parse error
  • ora-16596 : object not part of the Data Guard broker configuration
  • ora-24082 : propagation may still be happening for the schedule for QUEUE string and DESTINATION string
  • ora-16502 : the Data Guard broker operation succeeded with warnings
  • ora-24012 : cannot drop QUEUE_TABLE, some queues in string have not been dropped
  • ora-13284 : failure to copy geometry object for conversion in place
  • ora-26065 : check constraint cannot reference column, string, in direct path load
  • ora-28141 : error in creating audit index file
  • ora-25149 : Columns of UROWID type may not be indexed
  • ora-13460 : GeoRaster metadata SRS error
  • ora-16092 : dependent archive log destination is not active
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.