ORA-00213: cannot reuse control file; old file size string, string required

Cause : To reuse a control file, it must be the same size as the one previously used.

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

Either do not specify REUSE, or specify a matching combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses in the CREATE DATABASE or CREATE CONTROLFILE statement.

update : 24-08-2017
ORA-00213

ORA-00213 - cannot reuse control file; old file size string, string required
ORA-00213 - cannot reuse control file; old file size string, string required

  • ora-27191 : sbtinfo2 returned error
  • ora-01154 : database busy. Open, close, mount, and dismount not allowed now
  • ora-01622 : thread number must be specified - default not specific
  • ora-29951 : warning in the execution of ODCIINDEXSPLITPARTITION routine
  • ora-36637 : (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-32638 : Non unique addressing in MODEL dimensions
  • ora-09756 : osnpns: no port in the name server.
  • ora-38955 : Source platform string not cross platform compliant
  • ora-29833 : indextype does not exist
  • ora-13838 : invalid ADDRESS value
  • ora-32342 : The EXPLAIN_MVIEW facility failed to explain the materialized view statement
  • ora-24337 : statement handle not prepared
  • ora-07513 : sscgctl: $deq unexpected return on cancel of term. lock
  • ora-01493 : invalid SAMPLE size specified
  • ora-29910 : invalid callback operation
  • ora-12032 : cannot use rowid column from materialized view log on "string"."string"
  • ora-26516 : no push transaction acknowledgement
  • ora-28265 : NameSpace beginning with 'sys_' is not allowed
  • ora-36639 : (XSDUNION18) UNIQUE cannot be applied to this concat dimension because leaves workspace object and workspace object share the value number.
  • ora-30930 : NOCYCLE keyword is required with CONNECT_BY_ISCYCLE pseudocolumn
  • ora-29509 : incorrectly formed Java binary class definition
  • ora-33215 : (CINSERT07) You cannot add session-only values to the workspace object dimension.
  • ora-10914 : invalid TABLESPACE GROUP clause
  • ora-02212 : duplicate PCTFREE option specification
  • ora-08276 : No room in nameserver for pid
  • ora-13271 : error allocating memory for geometry object
  • ora-28541 : Error in HS init file on line number.
  • ora-13764 : Value "string" is illegal as a result percentage.
  • ora-16400 : quota attributes are not allowed with DB_RECOVERY_FILE_DEST
  • ora-12671 : Shared server: adapter failed to save context
  • 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.