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 : 28-05-2017
ORA-16069

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

  • ora-02843 : Invalid value for kernel flag
  • ora-12225 : TNS:destination host unreachable
  • ora-27503 : IPC error attempting to cancel request
  • ora-12574 : TNS:redirection denied
  • ora-24778 : cannot open connections
  • ora-28268 : Exceeded the maximum allowed size for Context information in a session
  • ora-27484 : Argument names are not supported for jobs without a program.
  • ora-28021 : cannot grant global roles
  • ora-31037 : Invalid XML attribute name string
  • ora-16075 : standby database destination mismatch
  • ora-12452 : label tag string already exists
  • ora-13801 : invalid value for SQLTUNE_CATEGORY parameter
  • ora-02197 : file list already specified
  • ora-24149 : invalid rule name
  • ora-02492 : missing required file block increment size in NEXT clause
  • ora-31483 : cannot have spaces in the parameter string
  • ora-00203 : using the wrong control files
  • ora-19254 : XQ0034 - too many declarations for function string
  • ora-04054 : database link string does not exist
  • ora-29304 : tablespace 'string' does not exist
  • ora-01536 : space quota exceeded for tablespace 'string'
  • ora-06749 : TLI Driver: option not allowed across network
  • ora-25251 : exceeded maximum number of recipients for message
  • ora-19554 : error allocating device, device type: string, device name: string
  • ora-10281 : maximum time to wait for process creation
  • ora-06744 : TLI Driver: listener cannot bind
  • ora-30435 : job_queue_processes must be non-zero in order to refresh summaries
  • ora-03216 : Tablespace/Segment Verification cannot proceed
  • ora-16754 : resource guard could not activate standby database
  • ora-36706 : (XSRELTBL07) workspace object should be dimensioned by workspace object and one level dimension.
  • 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.