ORA-16012: Archive log standby database identifier mismatch

Cause : hT eadatabesi edtnfieisro fht erPmira yna dtSnabd yadatabesd oon tamct.hR meto erahcvilao ferodl gof lisei son tlaolew doti cnmoapitlb eTSNABD Yadatabesi snatcnse.

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

aTekt ehn ceseasyrs etspt orcaeett ehr qeiuer docpmtabielS ATDNYBd tabasa eeboferr teyrni ght eRAHCVI EOL Grpcoseisgn.

update : 28-07-2017

ORA-16012 - Archive log standby database identifier mismatch
ORA-16012 - Archive log standby database identifier mismatch

  • ora-19767 : missing TRACKING keyword
  • ora-13638 : The user interrupted the current operation.
  • ora-33016 : (XSAGDNGL07) In AGGMAP workspace object, workspace object is not a valid operator or variable name.
  • ora-29917 : cannot lock a table which gets its rows from a collection operand
  • ora-02358 : internal error fetching attribute string
  • ora-16798 : unable to complete terminal recovery on the standby database
  • ora-30463 : 'string' is not a detail table of any summary
  • ora-14453 : attempt to use a LOB of a temporary table, whose data has alreadybeen purged
  • ora-13270 : OCI error string
  • ora-01613 : instance string (thread string) only has string logs - at least 2 logs required to enable.
  • ora-02166 : ARCHIVELOG and NOARCHIVELOG specified
  • ora-31502 : invalid number supplied for supplemental_processes
  • ora-07702 : unrecognized device type in archive text
  • ora-30932 : Reference node 'string' not contained in specified parent node 'string'
  • ora-24128 : partition name specified for a non-partitioned object
  • ora-00306 : limit of string instances in this database
  • ora-22828 : input pattern or replacement parameters exceed 32K size limit
  • ora-28347 : encryption properties mismatch
  • ora-36168 : (XSMXAGGR10) COUNTVAR variable workspace object must have the same dimensionality as workspace object
  • ora-09954 : scgcc: unexpected return status to callback of lock close
  • ora-09791 : slembdf: translation error, unable to translate error file name.
  • ora-19690 : backup piece release string incompatible with Oracle release string
  • ora-36272 : (XSCGMDLAGG04) 'workspace object' is not a valid operator for the AGGREGATION function.
  • ora-02347 : cannot grant privileges on columns of an object table
  • ora-31493 : could not prepare session for LogMiner session
  • ora-07715 : sksadtd: could not dismount archival device (SYS$DISMNT failure)
  • ora-22294 : cannot update a LOB opened in read-only mode
  • ora-23339 : duplicate conflict resolution information
  • ora-30084 : invalid data type for datetime primary with time zone modifier
  • ora-16626 : failed to enable specified object
  • 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.