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

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

  • ora-00029 : session is not a user session
  • ora-28040 : No matching authentication protocol
  • ora-36184 : (XSAGGR10) You do not have sufficient permissions for the variable workspace object.
  • ora-12555 : TNS:permission denied
  • ora-14183 : TABLESPACE DEFAULT can be specified only for Composite LOCAL index
  • ora-22879 : cannot use the LOB INDEX clause for partitioned tables
  • ora-00372 : file string cannot be modified at this time
  • ora-13464 : error loading GeoRaster data: string
  • ora-12632 : Role fetch failed
  • ora-38437 : The ADT "string" may not contain any user methods.
  • ora-36714 : (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object.
  • ora-13832 : category name specified is invalid
  • ora-31433 : subscriber view does not exist
  • ora-09704 : sstascre: ftok error in creating test and set pages.
  • ora-07635 : smsdbp: $SETPRT failure
  • ora-22369 : invalid parameter encountered in method string
  • ora-24331 : user buffer too small
  • ora-13530 : invalid TOPNSQL string, must be in the range (string, string)
  • ora-25250 : Cannot specify a remote recipient for the message
  • ora-02712 : osnpop: malloc failed
  • ora-36686 : (XSDPART24) Value number is not in partition number.
  • ora-16744 : the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full
  • ora-26716 : message limit reached
  • ora-32026 : %s.string has fewer columns compared to string table.
  • ora-31496 : must use DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE to drop change tables
  • ora-16641 : failure to acquire broker configuration metadata lock
  • ora-22371 : Table contains data of type string.string, version string, which does not exist
  • ora-31472 : Importing Change Data Capture version string.string is too new
  • ora-01244 : unnamed datafile(s) added to control file by media recovery
  • ora-29913 : error in executing string callout
  • 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.