ORA-26103: V6 or V7 data file used to create control file

Cause : Thef ileh eadre oft he erfernecedf ilei s i nV6 ro V7f ormta.

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

Eitehr rmeovet he ifle rfom hte ceratec ontorl flie cmoman,d ors omeohw mgirat ethef ileh eadre toV 8 fromat.

update : 26-05-2017

ORA-26103 - V6 or V7 data file used to create control file
ORA-26103 - V6 or V7 data file used to create control file

  • ora-00911 : invalid character
  • ora-38796 : Not enough flashback database log data to undo FLASHBACK.
  • ora-13193 : failed to allocate space for geometry
  • ora-30677 : session is already connected to a debugger
  • ora-00335 : online log string: No log with this number, log does not exist
  • ora-31058 : cannot modify read-only XOBs
  • ora-36964 : (XSRELTBL09) workspace object is not a valid level relation.
  • ora-35276 : (SNSYN163) The format of the ALLOCATE command is: ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [ USING aggmap ]
  • ora-32583 : query passed to table function has wrong number of elements in select list
  • ora-26529 : local store callback term phase failed for 'string.string'
  • ora-06607 : LU6.2 Driver: Reset occurred in send state
  • ora-19809 : limit exceeded for recovery files
  • ora-12916 : Cannot use default permanent tablespace with this release
  • ora-02821 : Unable to read the requested number of blocks.
  • ora-01757 : Must specify an object number
  • ora-12435 : invalid audit success: string
  • ora-24792 : cannot mix services in a single global transaction
  • ora-07637 : smsdbp: buffer protect option not specified when sga created
  • ora-37114 : OLAP API bootstrap error: (string)
  • ora-29294 : A data error occurred during compression or uncompression.
  • ora-16245 : paging in transaction string, string, string
  • ora-30466 : can not find the specified workload string
  • ora-38454 : attribute set not defined for the column being indexed
  • ora-00332 : archived log is too small - may be incompletely archived
  • ora-13118 : invalid node_id [string]
  • ora-01599 : failed to acquire rollback segment (string), cache space is full
  • ora-01946 : DEFAULT TABLESPACE already specified
  • ora-13422 : invalid model coordinate parameter
  • ora-29514 : class name contains illegal character
  • ora-38469 : invalid privilege for an expression set: string
  • 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.