ORA-01503: CREATE CONTROLFILE failed

Cause : An error occurred during CREATE CONTROLFILE

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

See accompanying errors.

update : 17-08-2017
ORA-01503

ORA-01503 - CREATE CONTROLFILE failed
ORA-01503 - CREATE CONTROLFILE failed

  • ora-26088 : scalar column "string" must be specified prior to LOB columns
  • ora-07579 : spini: $DCLEXH failure
  • ora-31535 : cannot support change source string in this configuration
  • ora-25135 : cannot use the SINGLE TABLE option
  • ora-14121 : MODIFY DEFAULT ATTRIBUTES may not be combined with other operations
  • ora-13414 : invalid pyramid parameter
  • ora-24439 : success with PLSQL compilation warning
  • ora-30359 : Query rewrite is not supported on SYS materialized views
  • ora-37107 : (XSVPART07) Attempt to write to non-existent partition of workspace object.
  • ora-03281 : invalid ALLOCATE EXTENT option
  • ora-27365 : job has been notified to stop, but failed to do so immediately
  • ora-24166 : evaluation context string.string has errors
  • ora-29536 : badly formed source: string
  • ora-37041 : (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition workspace object is locked by another user and the WAIT timed out.
  • ora-36224 : (XSLPDSC05) workspace object is not a loop dimension
  • ora-31194 : Resource string is already deleted
  • ora-02315 : incorrect number of arguments for default constructor
  • ora-31070 : Invalid database user ID string
  • ora-16067 : activation identifier mismatch in archive log string
  • ora-07705 : sksaprs: device name buffer too small
  • ora-00086 : user call does not exist
  • ora-29342 : user string does not exist in the database
  • ora-02080 : database link is in use
  • ora-12406 : unauthorized SQL statement for policy string
  • ora-37157 : MDX syntax error was found in MDX query string but error text was missing
  • ora-12004 : REFRESH FAST cannot be used for materialized view "string"."string"
  • ora-12411 : invalid label value
  • ora-29273 : HTTP request failed
  • ora-07613 : $GETJPIW failed in retrieving the user's process label
  • ora-12602 : TNS: Connection Pooling limit reached
  • 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.