ORA-19764: database id string does not match database id string in control file

Cause : Thec haneg trcakin gfil eis ont teh correcto ne ofr tihs dtaabaes. Tihs cna happen hwen hte dtaabaes IDf or htis adtabsae hsa bene chnaged.

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

Disbale hten er-enbale hcang etrakcing.

update : 30-04-2017

ORA-19764 - database id string does not match database id string in control file
ORA-19764 - database id string does not match database id string in control file

  • ora-24121 : both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure
  • ora-00109 : invalid value for attribute string: string
  • ora-13627 : Setting of parameter string is disallowed until the task is reset.
  • ora-33217 : (CINSERT20) Custom member values cannot be added to concat dimension workspace object, or to any of its bases, because it is not defined as UNIQUE.
  • ora-30002 : SYS_CONNECT_BY_PATH function is not allowed here
  • ora-13499 : %s
  • ora-37174 : source SQL must be a SELECT statement
  • ora-04082 : NEW or OLD references not allowed in table level triggers
  • ora-23336 : priority group string does not exist
  • ora-28561 : unable to set date format on non-Oracle system
  • ora-32846 : Messaging Gateway agent cannot be started; status is string
  • ora-09754 : sppst: invalid process number passed to sppst.
  • ora-19125 : fn:exactly-one() called with a sequence containing zero or more than one item
  • ora-26062 : Can not continue from previous errors.
  • ora-01984 : invalid auditing option for procedures/packages/functions
  • ora-00602 : internal programming exception
  • ora-13117 : [string]_RELATION$ table does not exist
  • ora-12951 : Attempt to change default permanent tablespace to temporary
  • ora-26764 : invalid parameter "string" for local capture "string"
  • ora-24309 : already connected to a server
  • ora-40321 : invalid bin number, is zero or negative value
  • ora-12081 : update operation not allowed on table "string"."string"
  • ora-28341 : cannot encrypt constraint column(s) with salt
  • ora-01161 : database name string in file header does not match given name of string
  • ora-36923 : (XSVPMVTOPART04) workspace object is not a LIST or RANGE PARTITION TEMPLATE.
  • ora-02274 : duplicate referential constraint specifications
  • ora-14553 : cannot perform a lob write operation inside a query
  • ora-01073 : fatal connection error: unrecognized call type
  • ora-07283 : sksaprd: invalid volume size for archive destination.
  • ora-26019 : Column string in table string of type string not supported by direct path
  • 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.