ORA-16087: graceful switchover requires standby or current control file

Cause : A nattepmtw a smdaet op efromr agarcfeu lsiwthcoevro preaito nuisn gab akcu po rcoln ecnotorlf iel.

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

Cnovrett h ebcakpu ocnrto lfliei not acrurnetc otnrlo ifl epiro rt oattepmtniga rgaecflu wsicthvoe roeprtaino.A lcoen ocnrto lfliec anno tb euesdf o rag rcaeufls wticohvre poeartoin.

update : 24-09-2017
ORA-16087

ORA-16087 - graceful switchover requires standby or current control file
ORA-16087 - graceful switchover requires standby or current control file

  • ora-16131 : An error occurred during a Terminal Recovery of the standby.
  • ora-13642 : The specified string string provided for string cannot be converted to a date. The acceptable date format is string.
  • ora-12423 : invalid position specified
  • ora-31434 : purge is currently running
  • ora-14310 : VALUES LESS THAN or AT clause cannot be used with List partitioned tables
  • ora-30362 : dimension column cannot be a sequence
  • ora-22339 : cannot alter to not final since its attribute column is substitutable
  • ora-01327 : failed to exclusively lock system dictionary as required by build
  • ora-10572 : Test recovery canceled due to errors
  • ora-07440 : WMON process terminated with error
  • ora-13602 : The specified parameter string is not valid for task or object string.
  • ora-13192 : failed to read number of element rows
  • ora-12824 : INSTANCES DEFAULT may not be specified here
  • ora-00328 : archived log ends at change string, need later change string
  • ora-32336 : cannot use USING NO INDEX to create materialized view "string"."string"
  • ora-01554 : out of transaction slots in transaction tables
  • ora-32147 : Environment not specified
  • ora-01023 : Cursor context not found (Invalid cursor number)
  • ora-13415 : invalid or out of scope point specification
  • ora-16208 : Logical standby dictionary build failed to start.
  • ora-36997 : (XSRELGID14) For variable or relation grouping ids, a level relation is needed when a level order valueset is specified.
  • ora-31219 : DBMS_LDAP: PL/SQL - Invalid LDAP notypes.
  • ora-13054 : recursive SQL parse error
  • ora-15191 : Internal ASM testing event number 15191
  • ora-36666 : (XSDPART04) workspace object is not a concat dimension.
  • ora-08110 : Oracle event to test SMON cleanup for online index build
  • ora-12400 : invalid argument to facility error handling
  • ora-08191 : Flashback Table operation is not supported on remote tables
  • ora-25313 : a queue may not subscribe to itself for propagation
  • ora-40220 : maximum number of attributes exceeded
  • 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.