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-05-2017

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-25955 : all tables must be joined in the where clause
  • ora-03008 : parameter COMPATIBLE >= string needed for string
  • ora-32826 : Messaging Gateway agent has already been started
  • ora-40221 : maximum target cardinality exceeded
  • ora-19589 : %s is not a snapshot or backup control file
  • ora-38423 : Attribute set created from an ADT may not be extended.
  • ora-39955 : invalid PL/SQL warning message number
  • ora-24078 : cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL
  • ora-31223 : DBMS_LDAP: cannot open more than string LDAP server connections
  • ora-16604 : unable to describe template using package "string"
  • ora-00601 : cleanup lock conflict
  • ora-14058 : partition number string: INITRANS value must be less than MAXTRANS value
  • ora-12455 : internal error in Label Security MMON cleanup task
  • ora-28522 : error initializing heterogeneous capabilities
  • ora-06771 : TLI Driver: error reading version
  • ora-06931 : CMX: error during read_properties for server
  • ora-26031 : index maintenance error, the load cannot continue
  • ora-06976 : X.25 Driver: endpoint creation failure
  • ora-12902 : default temporary tablespace must be SYSTEM or of TEMPORARY type
  • ora-36762 : (XSLANGDM02) You cannot modify the string property of %J because analytic workspace string is attached in MULTI mode.
  • ora-13851 : Tracing for client identifier string is already enabled
  • ora-19764 : database id string does not match database id string in control file
  • ora-09318 : slkhst: unable to host out to operating system
  • ora-28533 : Heterogeneous Services coercion handling error
  • ora-38477 : attribute set cannot be derived from an evolved type or a subtype.
  • ora-25965 : fact table must be included in the from clause
  • ora-39116 : invalid trigger operation on mutating table string.string
  • ora-31441 : table is not a change table
  • ora-01925 : maximum of string enabled roles exceeded
  • ora-08006 : specified row no longer exists
  • 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.