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

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

  • ora-08462 : raw buffer contains invalid decimal data
  • ora-19688 : control file autobackup format(string) for string does not have %F
  • ora-06578 : output parameter cannot be a duplicate bind
  • ora-29284 : file read error
  • ora-37134 : (XSCCOMP09) You cannot add new values to workspace object because it includes positions for precomputed aggregate values.
  • ora-29865 : indextype is invalid
  • ora-27202 : skgfpen: sbtpcend returned error
  • ora-12704 : character set mismatch
  • ora-14521 : Default tablespace string block size [string] for string string does not match existing string block size [string]
  • ora-36178 : (XSAGGR01) To be used with AGGREGATE, AGGMAP workspace object must be declared with the AGGMAP command.
  • ora-36861 : (XSTFRC01) SQL Cache ID parameter is invalid or missing.
  • ora-30654 : missing DEFAULT keyword
  • ora-23439 : refresh group template already exists
  • ora-25454 : error during evaluation of rule set: string.string for iterator: string
  • ora-39953 : the range value specified is beyond allowed range
  • ora-25189 : illegal ALTER TABLE option for an index-organized table
  • ora-02315 : incorrect number of arguments for default constructor
  • ora-22984 : view query cannot contain references to a super view
  • ora-31499 : null value specified for required parameter string
  • ora-06781 : TLI Driver: error reading negotation string
  • ora-32580 : both SYS and SYSTEM passwords must be provided
  • ora-29529 : invalid function or method call string in trigger string
  • ora-36612 : (XSLMS01) invalid OLAP message number: value
  • ora-01105 : mount is incompatible with mounts by other instances
  • ora-29277 : invalid SMTP operation
  • ora-00302 : limit of string logs exceeded
  • ora-24186 : wrong object type, could not transform message
  • ora-31466 : no publications found
  • ora-19379 : invalid time_limit or repeat_interval
  • ora-24355 : attempt to store a negative number in an Unsigned Display type.
  • 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.