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 : 21-08-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-38956 : Target platform string not cross platform compliant
  • ora-38709 : Recovery Area is not enabled.
  • ora-27415 : repeat interval or calendar must start with the FREQ= clause
  • ora-13142 : invalid PROXIMITY window definition
  • ora-08310 : sllfop: Bad value for recsize
  • ora-12425 : cannot apply policies or set authorizations for system schemas
  • ora-01166 : file number string is larger than string (string)
  • ora-00962 : too many group-by / order-by expressions
  • ora-32767 : No server connection for this operation
  • ora-31001 : Invalid resource handle or path name "string"
  • ora-02703 : osnpopipe: pipe creation failed
  • ora-14075 : partition maintenance operations may only be performed on partitioned indices
  • ora-00333 : redo log read error block string count string
  • ora-12217 : TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA
  • ora-00356 : inconsistent lengths in change description
  • ora-30385 : specified attribute relationship ('string' determines 'string') exists
  • ora-31460 : logfile location string is not an existing directory
  • ora-32056 : invalid number of extents
  • ora-02079 : no new sessions may join a committing distributed transaction
  • ora-12420 : required procedures and functions not in policy package "string"
  • ora-38774 : cannot disable media recovery - flashback database is enabled
  • ora-10587 : Invalid count for ALLOW n CORRUPTION option
  • ora-02188 : Cannot enable instance publicly
  • ora-03286 : ALLOCATE EXTENT not valid for HASH CLUSTERS
  • ora-24128 : partition name specified for a non-partitioned object
  • ora-28044 : unsupported directory type
  • ora-16955 : Unknown error during SQL analyze.
  • ora-13365 : layer SRID does not match geometry SRID
  • ora-30679 : JDWP-based debugging not supported in this configuration
  • ora-16259 : Switchover to logical standby requires a log archive destination
  • 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.