ORA-01610: recovery using the BACKUP CONTROLFILE option must be done

Cause : Eithe ran ealrier dtaabaser ecoveyr sessoin speicfied ABCKUP OCNTROLIFLE, o rthe cnotrol ifle wa srecretaed wiht the ERSETLOSG optino, or hte conrtol fiel bein gused si a bakcup cotnrol flie. Afetr tha tonly ABCKUP OCNTROLIFLE reocvery si alloewd andi t mus tbe followed yb a lo greseta t then ext dtaabaseo pen.

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

Perfomr recoevry usnig theB ACKUPC ONTROIFLE opiton.

update : 26-09-2017
ORA-01610

ORA-01610 - recovery using the BACKUP CONTROLFILE option must be done
ORA-01610 - recovery using the BACKUP CONTROLFILE option must be done

  • ora-30951 : Element or attribute at Xpath string exceeds maximum length
  • ora-14306 : List value 'string' specified twice in partitions 'string', 'string'
  • ora-08178 : illegal SERIALIZABLE clause specified for user INTERNAL
  • ora-38750 : FLASHBACK DATABASE may not be performed using a dispatcher.
  • ora-02876 : smpini: Unable to attach to shared memory for PGA
  • ora-25289 : Buffer Already Exists
  • ora-13420 : the SRID of the geometry parameter was not null
  • ora-16633 : the only instance of the database cannot be removed
  • ora-38857 : cannot mark redo thread string as enabled
  • ora-21708 : inappropriate operation on a transient object
  • ora-29256 : Cursor contains both regular and array defines which is illegal
  • ora-39959 : invalid warning number (string)
  • ora-06102 : NETTCP: cannot allocate context area
  • ora-12233 : TNS:Failure to accept a connection
  • ora-25952 : join index must only contain inner equi-joins
  • ora-14610 : Lob attributes not specified for lob column string for subpartition string
  • ora-07641 : smscre: Unable to use the system pagefile for the SGA
  • ora-01575 : timeout waiting for space management resource
  • ora-29970 : Specified registration id does not exist
  • ora-33060 : (XSAGDNGL29) In AGGMAP workspace object, the value for the ERRORLOG MAX option must be greater than 0.
  • ora-21612 : key is already being used
  • ora-31508 : invalid parameter value for synchronous change set
  • ora-14632 : cannot specify PARALLEL clause when adding a List subpartition
  • ora-12497 : maximum combined categories exceeds string
  • ora-21503 : program terminated by fatal error
  • ora-01782 : UNRECOVERABLE cannot be specified for a cluster or clustered table
  • ora-14110 : partitioning column may not be of type ROWID
  • ora-06258 : NETNTT: cannot allocate context area
  • ora-12024 : materialized view log on "string"."string" does not have primary key columns
  • ora-12926 : FORCE LOGGING option already specified
  • 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.