ORA-00215: must be at least one control file

Cause : No conrtol fil eis speicfied o rthe cotnrol fiel speciifed doe snot exsit.

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

Specif yat leats one vlaid conrtol fil eand rerty the poeratio.n

update : 23-01-2017
ORA-00215

ORA-00215 - must be at least one control file
ORA-00215 - must be at least one control file

  • ora-36720 : (XSALLOC01) To be used with ALLOCATE, your AGGMAP workspace object must be defined with the ALLOCMAP command.
  • ora-00076 : dump string not found
  • ora-38787 : Creating the first guaranteed restore point requires mount mode when flashback database is off.
  • ora-32109 : invalid column or parameter position
  • ora-23376 : node string is not compatible with replication version "string"
  • ora-01901 : ROLLBACK keyword expected
  • ora-32310 : object materialized views must select from an object table
  • ora-09870 : spini: failure initializing maximum number of open files.
  • ora-16718 : failed to locate database object
  • ora-13288 : point coordinate transformation error
  • ora-02397 : exceeded PRIVATE_SGA limit, you are being logged off
  • ora-22909 : exceeded maximum VARRAY limit
  • ora-22890 : cannot specify name for REF column constraint
  • ora-19334 : Invalid column specification for CREATE_DBURI operator
  • ora-32629 : measure used for referencing cannot be updated
  • ora-09293 : sksasmo: unable to send message to console
  • ora-38430 : Operation "string" not supported in the current release.
  • ora-19557 : device error, device type: string, device name: string
  • ora-00225 : expected size string of control file differs from actual size string
  • ora-19634 : filename required for this function
  • ora-32121 : Source FILE is null
  • ora-04052 : error occurred when looking up remote object stringstringstringstringstring
  • ora-01582 : unable to open control file for backup
  • ora-13776 : User "string" has not been granted the "SELECT" privilege on the "SQL tuning set" DBA views.
  • ora-24331 : user buffer too small
  • ora-10944 : trace name context forever
  • ora-31655 : no data or metadata objects selected for job
  • ora-38611 : FI input cursor's item type is not supported
  • ora-14253 : table is not partitioned by Composite Range method
  • ora-23389 : obsolete procedure; drop objects and recreate using new master
  • 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.