ORA-16047: DGID mismatch between destination setting and standby

Cause : Teh BD_NUIUQEN_AEM pseicfeidf o rteh edsitntaino ode snto amthc hteD BU_NQIU_ENMAEa tt h edsetniaito.n

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

Mkaes uer hteD BU_NQIU_ENMAEs pceiife di nteh OLGA_RHCIEV_EDS_Tnp aarmtee rdfeiendf o rteh edsitntaino amthce steh BD_NUIUQEN_AEM aprmaeetrd eifnde ta hted etsiantoin.

update : 25-06-2017
ORA-16047

ORA-16047 - DGID mismatch between destination setting and standby
ORA-16047 - DGID mismatch between destination setting and standby

  • ora-19679 : RMAN configuration number string is outside valid range of 1 through string
  • ora-13770 : Baseline "string" does not exist.
  • ora-30158 : The OCIFileWrite causes the file to exceed the maximum allowed size
  • ora-16741 : the destination parameter of standby database "string" has incorrect syntax
  • ora-16006 : audit_trail destination incompatible with database open mode
  • ora-00152 : current session does not match requested session
  • ora-25193 : cannot use COMPRESS option for a single column key
  • ora-30514 : system trigger cannot modify tablespace being made read only
  • ora-19716 : error processing format string to generate name for backup
  • ora-34276 : (MXDCL33) (Precision, Scale) arguments can only be used with a NUMBER variable or dimension.
  • ora-12096 : error in materialized view log on "string"."string"
  • ora-30678 : too many open connections
  • ora-16587 : ambiguous object specified to Data Guard broker
  • ora-00211 : control file does not match previous control files
  • ora-38416 : A stored attribute may not be longer then 300 characters.
  • ora-32109 : invalid column or parameter position
  • ora-23534 : missing column in materialized view container table "string"."string"
  • ora-16247 : DDL skipped on internal schema
  • ora-01104 : number of control files (string) does not equal string
  • ora-01662 : tablespace 'string' is non-empty and cannot be made temporary
  • ora-16800 : redo transport service for a standby database incorrectly set to ALTERNATE
  • ora-13433 : GeoRaster metadata default RGB error
  • ora-16623 : stale DRC UID sequence number detected
  • ora-30476 : PLAN_TABLE does not exist in the user's schema
  • ora-19809 : limit exceeded for recovery files
  • ora-06408 : NETCMN: incorrect message format
  • ora-26650 : %s background process string might not be started successfully
  • ora-12700 : invalid NLS parameter value (string)
  • ora-19665 : size string in file header does not match actual file size of string
  • ora-03001 : unimplemented feature
  • 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.