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 : 23-08-2017
ORA-16069

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

  • ora-12566 : TNS:protocol error
  • ora-16764 : redo transport service to a standby database is offline
  • ora-01281 : SCN range specified is invalid
  • ora-23337 : priority or value not in priority group string
  • ora-01875 : time zone minute must be between -59 and 59
  • ora-08274 : Out of memory for environment variable
  • ora-26723 : user "string" requires the role "string"
  • ora-30973 : invalid Path Table option for XML Index
  • ora-16081 : insufficient number of processes for APPLY
  • ora-31412 : change set string is disabled and cannot be advanced
  • ora-16735 : error executing dbms_logstdby.unskip_error procedure
  • ora-27013 : skgfqdel: cannot delete an open file
  • ora-12727 : invalid back reference in regular expression
  • ora-13136 : null common code generated
  • ora-07624 : smsdes: $DGBLSC failure
  • ora-16780 : a database has exhausted its archived redo log storage quota
  • ora-30342 : referenced level is not defined in this dimension
  • ora-24064 : propagation for QUEUE string and DESTINATION string already enabled
  • ora-24195 : attemp to retrieve the name list of a map message with size exceeding 1024
  • ora-25269 : cant specify sognature with get signature option
  • ora-27415 : repeat interval or calendar must start with the FREQ= clause
  • ora-22887 : type of REF column is not the same as that of its scoped table
  • ora-15045 : ASM file name 'string' is not in reference form
  • ora-01913 : EXCLUSIVE keyword expected
  • ora-14103 : LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE
  • ora-28108 : circular security policies detected
  • ora-29363 : plan directive string, string is mandatory and cannot be modified or deleted
  • ora-39086 : cannot retrieve job information
  • ora-03216 : Tablespace/Segment Verification cannot proceed
  • ora-29397 : cannot grant/revoke switch privilege for string
  • 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.