ORA-16771: failover to a physical standby database failed

Cause : In the failover operation, the step of converting the physical standby database to the primary database failed.

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

Check the alert log and the Data Guard broker log for more details about the error.

update : 27-05-2017

ORA-16771 - failover to a physical standby database failed
ORA-16771 - failover to a physical standby database failed

  • ora-29346 : invalid tablespace list
  • ora-31502 : invalid number supplied for supplemental_processes
  • ora-01313 : LogMiner dictionary column type different from specified type
  • ora-04066 : non-executable object, string
  • ora-01935 : missing user or role name
  • ora-06130 : NETTCP: host access denied
  • ora-12664 : Services required by server not available on the client
  • ora-01687 : specified logging attribute for tablespace 'string' is same as the existing
  • ora-10630 : Illegal syntax specified with SHRINK clause
  • ora-00358 : Too many file members specified, the maximum is string
  • ora-37044 : (XSACQUIRE_OLDGEN) Cannot acquire object workspace object without resync.
  • ora-25250 : Cannot specify a remote recipient for the message
  • ora-07598 : spwat: $SETIMR failure
  • ora-12554 : TNS:current operation is still in progress
  • ora-22632 : AnyDataSet parameter is not valid for the current operation
  • ora-09760 : osnpui: cannot send break message
  • ora-02777 : Stat failed on log directory
  • ora-12537 : TNS:connection closed
  • ora-06255 : NETNTT: cannot read pid of remote process
  • ora-39780 : Direct path context operations are not allowed after the context is aborted or finished
  • ora-16182 : Internal error on internal channel during remote archival
  • ora-39211 : unable to retrieve dumpfile information as specified
  • ora-28515 : cannot get external object definitions from string
  • ora-12712 : new character set must be a superset of old character set
  • ora-00705 : inconsistent state during start up; shut down the instance, then restart it
  • ora-02398 : exceeded procedure space usage
  • ora-13116 : [string]_FACE$ table does not exist
  • ora-06032 : NETDNT: connect failed, access control data rejected
  • ora-24755 : OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported
  • ora-26515 : no master log available for 'string.string'
  • 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.