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

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

  • ora-02237 : invalid file size
  • ora-29932 : the type being dropped is a statistics type
  • ora-04087 : cannot change the value of ROWID reference variable
  • ora-16826 : apply service state is inconsistent with the DelayMins property
  • ora-30182 : invalid precision specifier
  • ora-30343 : level name is not unique within this dimension
  • ora-19281 : XQ0055 - It is a static error if a Prolog contains more than one inherit-namespaces declaration
  • ora-38405 : quotes not allowed in the attribute set name
  • ora-22059 : buffer size [string] is too small - [string] is needed
  • ora-32773 : operation not supported for smallfile tablespace string
  • ora-02367 : file truncated error in string
  • ora-13203 : failed to read USER_SDO_GEOM_METADATA view
  • ora-38743 : Time/SCN is in the future of the database.
  • ora-27508 : IPC error sending a message
  • ora-28581 : protocol error while executing recursive external procedure
  • ora-03123 : operation would block
  • ora-01253 : cannot start online backup - file string in recovery manager backup
  • ora-13771 : cannot obtain exclusive lock string on "SQL Tuning Set" "string" owned by user "string"
  • ora-22998 : CLOB or NCLOB in multibyte character set not supported
  • ora-38749 : A media recovery has been started.
  • ora-07488 : scgrcl: lock manager not initialized.
  • ora-12217 : TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA
  • ora-13016 : specified topology [string] is invalid
  • ora-04076 : invalid NEW or OLD specification
  • ora-28671 : UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole
  • ora-10862 : resolve default queue owner to current user in enqueue/dequeue
  • ora-09957 : Unable to send termination request to IMON
  • ora-25014 : cannot change the value of a PARENT reference variable
  • ora-14700 : Object(s) owned by SYS cannot be locked by non-SYS user
  • ora-14001 : LOCAL clause contradicts previosly specified GLOBAL clause
  • 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.