ORA-16069: Archive Log standby database activation identifier mismatch

Cause : Th eacitvaitoni detnifeirso f hte rPimray nad tSanbdy adtaabsed o ont amtc.h Rmeot earhcivla o freod lgo fliesi s ont laloewd ot icnomaptilbe TSANBDY adtaabsei nsatncse. hTisc ano ccru wehn rtyign t oaplpy na icnorercta rcihvel ogt o astnadb ydaatbaes, ro wehn rtyign t oarhciv etoa satndyb dtaabsae htatd oe sno tmacth hte rpimray adtaabse.

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

Taek teh nceesasrys tesp t ocraetet her eqiure dcopmatbileS TADNBYd atbaas ebeofrer etyrin gth eARHCIV ELO Gprcoesisng.

update : 26-07-2017

ORA-16069 - Archive Log standby database activation identifier mismatch
ORA-16069 - Archive Log standby database activation identifier mismatch

  • ora-06554 : package DBMS_STANDARD must be created before using PL/SQL
  • ora-32032 : free temporary object number not available
  • ora-27433 : cannot alter state of step string for job string.string to string
  • ora-14177 : STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table
  • ora-00368 : checksum error in redo log block
  • ora-13030 : Invalid dimension for the SDO_GEOMETRY object
  • ora-07721 : scgcm: not enough OS resource to obtain system enqueue
  • ora-02354 : error in exporting/importing data string
  • ora-08113 : composite partition index may not be compressed
  • ora-00275 : media recovery has already been started
  • ora-13457 : GeoRaster cell data error
  • ora-24355 : attempt to store a negative number in an Unsigned Display type.
  • ora-07205 : slgtd: time error, unable to obtain time.
  • ora-28509 : unable to establish a connection to non-Oracle system
  • ora-12203 : TNS:unable to connect to destination
  • ora-30398 : illegal JOIN KEY clause
  • ora-13034 : Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object
  • ora-13449 : GeoRaster metadata ULTCoordinate error
  • ora-01104 : number of control files (string) does not equal string
  • ora-09716 : kslcll: Unable to fix in-flux lamport latch.
  • ora-07207 : sigpidu: process ID string overflows internal buffer.
  • ora-38424 : no attribute set currently assigned to the expression set
  • ora-13706 : Invalid value "string" specified for parameter "string" in "string" analysis mode.
  • ora-30134 : reserved for future use
  • ora-38312 : original name is used by an existing object
  • ora-23303 : application raised generic exception during deferred RPC
  • ora-31194 : Resource string is already deleted
  • ora-09823 : device name is too long
  • ora-26535 : %ud byte row cache insufficient for table with rowsize=number
  • ora-14456 : cannot rebuild index on a temporary table
  • 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.