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 : 24-09-2017

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

  • ora-29820 : the statistics type is not present
  • ora-38422 : invalid datatype for the attribute: string
  • ora-02292 : integrity constraint (string.string) violated - child record found
  • ora-31460 : logfile location string is not an existing directory
  • ora-23485 : Column group "string" must consist of a single numeric column only
  • ora-27012 : skgfrd: read from file failed
  • ora-26727 : Cannot alter queue_to_queue property of existing propagation.
  • ora-19628 : invalid SCN range
  • ora-15023 : reached maximum allowable number of disks string
  • ora-19728 : data object number conflict between table string and partition string in table string
  • ora-08103 : object no longer exists
  • ora-19687 : SPFILE not found in backup set
  • ora-16709 : standby archived log location settings conflict with flash recovery area
  • ora-00029 : session is not a user session
  • ora-14027 : only one PARTITION clause may be specified
  • ora-23415 : materialized view log for "string"."string" does not record the primary key
  • ora-38452 : Expression Filter index name may not be longer than 25 characters
  • ora-38491 : could not evaluate subexpression for rowid "string"
  • ora-26078 : file "string" is not part of database being loaded
  • ora-19041 : Comment data cannot contain two consecutive '-'s
  • ora-38781 : cannot disable media recovery - have guaranteed restore points
  • ora-14501 : object is not partitioned
  • ora-12828 : Can't start parallel transaction at a remote site
  • ora-14625 : subpartition contains rows corresponding to values being dropped
  • ora-31431 : all source tables must belong to the synchronous change set
  • ora-03287 : invalid FREELIST GROUP specified
  • ora-39782 : Direct path prepare is not allowed after another context loading the same table has ended
  • ora-37153 : unknown exception caught: (case string)
  • ora-25190 : an index-organized table maintenance operation may not be combined with other operations
  • ora-27000 : skgfqsbi: failed to initialize storage subsystem (SBT) layer
  • 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.