ORA-16217: prepare to switchover has not completed

Cause : A nATLE RDTAAABS EPERPRAET OS WTICOHVRE ocmamn dwsa siseud ,btu htep rpeaer catviiyt iddn o tcmopelt.e

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

Vreiyf hta tteh tsadnb ywsa rpeaprde rpoepryl.Y o umya acneclt h eperpraea n dprefroma nu nrpeaprde wsicthvoe rwihc hrqeurie sad aatbsael ikn ot ocmlpeet.O rr esiseu htep rpeaer poeartoino nt h esatnbdy.

update : 25-04-2017
ORA-16217

ORA-16217 - prepare to switchover has not completed
ORA-16217 - prepare to switchover has not completed

  • ora-01696 : control file is not a clone control file
  • ora-07339 : spcre: maximum number of semaphore sets exceeded.
  • ora-24389 : Invalid scrollable fetch parameters
  • ora-24404 : connection pool does not exist
  • ora-01657 : invalid SHRINK option value
  • ora-02829 : No segment of the proper size is available
  • ora-32035 : unreferenced query name defined in WITH clause
  • ora-06561 : given statement is not supported by package DBMS_SQL
  • ora-23515 : materialized views and/or their indices exist in the tablespace
  • ora-29928 : duplicate default selectivity specified
  • ora-01117 : adding file 'string' with illegal block size: string; limit is string
  • ora-08001 : maximum number of sequences per session exceeded
  • ora-01115 : IO error reading block from file string (block # string)
  • ora-07629 : smpall: $EXPREG failure
  • ora-07672 : $PARSE_CLASS failed translating the string into a binary label
  • ora-15040 : diskgroup is incomplete
  • ora-39212 : installation error: XSL stylesheets not loaded correctly
  • ora-14134 : indexes cannot use both DESC and REVERSE
  • ora-23317 : a communication failure has occurred
  • ora-39751 : partitioned table on both sides of PARTITIONED OUTER JOIN is not supported
  • ora-26063 : Can not flashback to specified SCN value - Wrap: string Base: string.
  • ora-06316 : IPA: Invalid database SID
  • ora-16221 : history table synchronization error
  • ora-09803 : Allocation of string buffer failed.
  • ora-30679 : JDWP-based debugging not supported in this configuration
  • ora-00360 : not a logfile member: string
  • ora-01113 : file string needs media recovery
  • ora-02372 : data for row: string
  • ora-15066 : offlining disk "string" may result in a data loss
  • ora-24149 : invalid rule name
  • 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.