ORA-01122: database file string failed verification check

Cause : The information in this file is inconsistent with information from the control file. See accompanying message for reason.

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

Make certain that the db files and control files are the correct files for this database.

update : 26-09-2017

ORA-01122 - database file string failed verification check
ORA-01122 - database file string failed verification check

  • ora-24750 : incorrect size of attribute
  • ora-12407 : unauthorized operation for policy string
  • ora-12055 : materialized view definition contains cyclic dependencies with existing materialized views
  • ora-01317 : Not attached to a Logminer session
  • ora-31448 : invalid value for change_source
  • ora-39785 : SQL expressions returning ADT objects are not allowed in direct path
  • ora-23610 : internal dbms_streams_tablespaces error: [string] [string] [string] [string]
  • ora-21613 : key does not exist
  • ora-40108 : input data contains too few distinct target (string) values
  • ora-23612 : unable to find tablespace "string"
  • ora-01026 : multiple buffers of size > 4000 in the bind list
  • ora-28545 : error diagnosed by Net8 when connecting to an agent
  • ora-19252 : XQ0032 - too many declarations for base URI
  • ora-06537 : OUT bind variable bound to an IN position
  • ora-14024 : number of partitions of LOCAL index must equal that of the underlying table
  • ora-14103 : LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE
  • ora-30159 : OCIFileOpen: Cannot create the file or cannot open in the requested mode
  • ora-12811 : PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, string
  • ora-01624 : log string needed for crash recovery of instance string (thread string)
  • ora-22332 : a dependent object in schema "string" has errors. string
  • ora-23608 : invalid resolution column "string"
  • ora-31491 : could not add logfile to LogMiner session
  • ora-07617 : $FORMAT_CLASS failed translating the binary label to a string
  • ora-12660 : Encryption or crypto-checksumming parameters incompatible
  • ora-38761 : redo log sequence string in thread string, incarnation string could not be accessed
  • ora-09749 : pws_look_up: port lookup failure
  • ora-36643 : (XSDUNION21) Concat dimension workspace object cannot be changed to NOT UNIQUE because it contains custom member values.
  • ora-08274 : Out of memory for environment variable
  • ora-19716 : error processing format string to generate name for backup
  • ora-12007 : materialized view reuse parameters are inconsistent
  • 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.