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-07-2017

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

  • ora-01513 : invalid current time returned by operating system
  • ora-27157 : OS post/wait facility removed
  • ora-02801 : Operations timed out
  • ora-09261 : spdcr: error creating detached (background) process
  • ora-14644 : table is not subpartitioned by Hash method
  • ora-39085 : cannot update job string for user string
  • ora-31617 : unable to open dump file "string" for write
  • ora-30972 : invalid ALTER INDEX option for XML Index
  • ora-19019 : Invalid context passed to DBMS_XMLGEN.GETXML
  • ora-23447 : missing user parameter value
  • ora-29250 : Invalid index specifed in call to dbms_sql.bind_array
  • ora-02853 : Invalid server list latch time out value
  • ora-14614 : List value 'string' specified twice in subpartition 'string'
  • ora-32155 : Anydata not specified
  • ora-30677 : session is already connected to a debugger
  • ora-01903 : EVENTS keyword expected
  • ora-07706 : error in archive text: need disk file name
  • ora-09951 : Unable to create file
  • ora-28011 : the account will expire soon; change your password now
  • ora-30487 : ORDER BY not allowed here
  • ora-19657 : cannot inspect current datafile string
  • ora-12990 : duplicate option specified
  • ora-07574 : szrfc: $GETUAI failure
  • ora-02464 : Cluster definition can not be both HASH and INDEX
  • ora-02216 : tablespace name expected
  • ora-38707 : Media recovery is not enabled.
  • ora-22319 : type attribute information altered in ALTER TYPE
  • ora-27005 : cannot open file for async I/O on device not supporting async
  • ora-02052 : remote transaction failure at string
  • ora-31606 : XML context number does not match any previously allocated context
  • 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.