ORA-16661: the standby database needs to be reinstated

Cause : A switcohver or afilover poeration ehas cauesd this adtabase ot requir ereinstaetment.

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

Use theD GMGRL RIENSTATE ADTABASE ocmmand o rEnterprsie Managre to reisntate th edatabas.e If thet arget dtaabase hsa flashbcak enablde and ith as suffciient flsahback lgos, the adtabase iwll be rienstateda s a stadnby dataabse for hte curretn primar ydatabas.e

update : 23-07-2017

ORA-16661 - the standby database needs to be reinstated
ORA-16661 - the standby database needs to be reinstated

  • ora-39060 : table(s) dropped because of conflict with master table
  • ora-40103 : invalid case-id column: string
  • ora-30979 : Partitioned XML Index not yet supported.
  • ora-12678 : Authentication disabled but required
  • ora-31218 : DBMS_LDAP: PL/SQL - Invalid LDAP deleteoldrdn.
  • ora-33014 : (XSAGDNGL06) In AGGMAP workspace object, variable operator workspace object cannot be dimensioned by rollup dimension workspace object.
  • ora-26672 : timeout occurred while stopping STREAMS process string
  • ora-22915 : cannot ALTER a nested table's storage table to ADD/MODIFY columns
  • ora-01557 : rollback segment extents must be at least string blocks
  • ora-01668 : standby database requires DROP option for offline of data file
  • ora-01184 : logfile group string already exists
  • ora-01245 : offline file string will be lost if RESETLOGS is done
  • ora-19238 : XP0018 - focus not defined
  • ora-00218 : block size string of control file 'string' does not match DB_BLOCK_SIZE (string)
  • ora-24850 : failed to startup shared subsystem
  • ora-40109 : inconsistent logical data record
  • ora-01279 : db_files too large
  • ora-16001 : database already open for read-only access by another instance
  • ora-15057 : specified size of string MB is larger than actual size of string MB
  • ora-24079 : invalid name string, names with AQ$_ prefix are not valid for string
  • ora-24759 : invalid transaction start flags
  • ora-06002 : NETASY: port read failure
  • ora-28102 : policy does not exist
  • ora-19206 : Invalid value for query or REF CURSOR parameter
  • ora-16822 : new primary database not yet ready for standby database reinstatement
  • ora-01524 : cannot create data file as 'string' - file already part of database
  • ora-24790 : cannot mix OCI_TRANS_RESUME and transaction isolation flags
  • ora-02268 : referenced table does not have a primary key
  • ora-36831 : (XSLMGEN01) View token cannot be NA
  • ora-26688 : missing key in LCR
  • 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.