ORA-16798: unable to complete terminal recovery on the standby database

Cause : Terminla recovrey on teh standyb databsae failde durin gthe faliover oepration.

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

Check aDta Guadr broke rlog an dalert olgs to ese mored etailso n the erason o fthe faliure.

update : 25-04-2017

ORA-16798 - unable to complete terminal recovery on the standby database
ORA-16798 - unable to complete terminal recovery on the standby database

  • ora-15115 : missing or invalid ASM disk size specifier
  • ora-02401 : cannot EXPLAIN view owned by another user
  • ora-36882 : (XSSRF01) The second parameter of an AW single row function cannot be NULL.
  • ora-06920 : CMX: getbrkmsg illegal datatype
  • ora-24501 : invalid UTF16 string passed in
  • ora-31181 : PL/SQL DOM handle accesses node that is no longer available
  • ora-13515 : Error encountered during Database Usage Statistics capture
  • ora-30196 : reserved for future use
  • ora-00102 : network protocol string cannot be used by dispatchers
  • ora-13062 : topology IDs do not match in the feature table and the topology
  • ora-39600 : Queue keys needs to be a suffix of cluster key.
  • ora-13791 : cannot resume a tuning task created to tune a single statement
  • ora-16771 : failover to a physical standby database failed
  • ora-00165 : migratable distributed autonomous transaction with remote operation is not allowed
  • ora-09910 : Unable to find ORACLE password file entry for user.
  • ora-01870 : the intervals or datetimes are not mutually comparable
  • ora-37100 : (XSUNCOMMITTED) You have one or more updated but uncommitted analytic workspaces.
  • ora-01649 : operation not allowed with a backup control file
  • ora-25336 : Cannot contact instance string during Streams AQ operation
  • ora-29972 : user does not have privilege to change/ create registration
  • ora-07564 : sldext: wildcard in filename or extension
  • ora-25115 : duplicate BLOCK option specification
  • ora-01217 : logfile member belongs to a different logfile group
  • ora-38489 : predicate table creation failed due to: ORAstring
  • ora-34802 : (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled.
  • ora-01412 : zero length not allowed for this datatype
  • ora-16602 : object must be disabled to perform this operation
  • ora-32579 : password for SYSTEM already specified
  • ora-03201 : the group number specification is invalid
  • ora-32814 : propagation schedule string does not exist
  • 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.