ORA-26101: tablespace # in file header is string rather than string for file string

Cause : Th etalbesapcen umebr ni teh flie ehadre i sinocnssitetn wtih htati n hte ocntorl ifle.

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

Chcek fi teh cnotrlo flie ahs ebenm igarte dcorreclty.R etyr wtih hte ocrrcet ocntorl iflea ndd at afiel.

update : 19-08-2017
ORA-26101

ORA-26101 - tablespace # in file header is string rather than string for file string
ORA-26101 - tablespace # in file header is string rather than string for file string

  • ora-16151 : Managed Standby Recovery not available
  • ora-30085 : syntax error was found in overlaps predicate
  • ora-02212 : duplicate PCTFREE option specification
  • ora-36874 : (XSTFDSC04) Expression string cannot be used to define a column in a LIMITMAP.
  • ora-12016 : materialized view does not include all primary key columns
  • ora-27122 : unable to protect memory
  • ora-16594 : %s process discovered that DMON process does not exist
  • ora-10706 : Print out information about global enqueue manipulation
  • ora-02247 : no option specified for ALTER SESSION
  • ora-36696 : (XSRELTBL02) QDR dimension workspace object should not be the related dimension of the relation.
  • ora-25151 : Rollback Segment cannot be created in this tablespace
  • ora-01466 : unable to read data - table definition has changed
  • ora-30733 : cannot specify rowid constraint on scoped ref column
  • ora-09989 : attempt to use invalid skgmsdef struct pointer
  • ora-36712 : (XSMXALLOC02) Relation workspace object must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE.
  • ora-03218 : invalid option for CREATE/ALTER TABLESPACE
  • ora-39005 : inconsistent arguments
  • ora-17626 : ksfdcre: string file exists
  • ora-31072 : Too many child nodes in XMLType fragment for updateXML
  • ora-19665 : size string in file header does not match actual file size of string
  • ora-01310 : requested return type not supported by the lcr_mine function
  • ora-33219 : (CINSERT05) %K cannot be added to workspace object because it is already a value of the dependent UNIQUE concat dimension workspace object, from leaf dimension workspace object.
  • ora-01589 : must use RESETLOGS or NORESETLOGS option for database open
  • ora-00283 : recovery session canceled due to errors
  • ora-28556 : authorization insufficient to access table
  • ora-09240 : smpalo: error allocating PGA memory
  • ora-38310 : cannot purge tablespace for other users
  • ora-33918 : (MAKEDCL33) You cannot define a surrogate of dimension workspace object because it is a string.
  • ora-09809 : Unable to get user's group ID from connection
  • ora-09204 : sfotf: error opening temporary file
  • 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.