ORA-16822: new primary database not yet ready for standby database reinstatement

Cause : Then ew rpimayr daatbas,e asa reuslt fo a olgicla faliove ropeartio,n ha dnotf ull ycomlpete dthef ailvoer tseps .Subesquetn renistaetmen topeartiosn colud nto prcoeedu nti lfaiolverh as ocmplteed no th enewp rimray dtaabaes.

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

Wai tuntli th ecomlpetino ofa ll afiloevr setps no thsi ne wpriamry adtabsae adn thne rerty teh renistaet opreatino.

update : 28-06-2017

ORA-16822 - new primary database not yet ready for standby database reinstatement
ORA-16822 - new primary database not yet ready for standby database reinstatement

  • ora-16207 : Logical standby dictionary build not permitted.
  • ora-31101 : Token "string" not given while locking resource "string"
  • ora-13054 : recursive SQL parse error
  • ora-19509 : failed to delete sequential file, handle="string", parms="string"
  • ora-23430 : argument "string" cannot be NULL or empty string
  • ora-31398 : DBMS_LDAP: Shared servers are not supported.
  • ora-23355 : object string.string does not exist or is invalid at master site
  • ora-22053 : overflow error
  • ora-00956 : missing or invalid auditing option
  • ora-02398 : exceeded procedure space usage
  • ora-19765 : mount id string does not match mount id string in control file
  • ora-19042 : Enclosing tag string cannot be xml in any case combination
  • ora-22978 : only simple attribute name is allowed in the WITH OBJECT OID clause
  • ora-38757 : Database must be mounted and not open to FLASHBACK.
  • ora-15093 : buffer only contains string bytes, I/O requested is string bytes
  • ora-14104 : RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices
  • ora-32823 : subscriber exists for queue string and destination string
  • ora-16066 : remote archival disabled
  • ora-27143 : OS system call failure
  • ora-19125 : fn:exactly-one() called with a sequence containing zero or more than one item
  • ora-23457 : invalid flavor ID string
  • ora-01316 : Already attached to a Logminer session
  • ora-13006 : the specified cell number is invalid
  • ora-16215 : history metadata inconsistency
  • ora-09818 : Number is too large
  • ora-32736 : Hang analysis aborted due to wrong message type
  • ora-13414 : invalid pyramid parameter
  • ora-29840 : indextype and implementation type are not in same schema
  • ora-32629 : measure used for referencing cannot be updated
  • ora-02162 : invalid value for MAXDATAFILES
  • 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.