Cause : An error occurred during CREATE CONTROLFILE

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

See accompanying errors.

update : 24-04-2017


  • ora-09369 : Windows 3.1 Two-Task driver bad instance handle
  • ora-23439 : refresh group template already exists
  • ora-32304 : materialized views with user-defined types cannot use prebuilt table
  • ora-02396 : exceeded maximum idle time, please connect again
  • ora-07283 : sksaprd: invalid volume size for archive destination.
  • ora-06320 : IPA: Remote maximum number of connections exceeded
  • ora-01579 : write error occurred during recovery
  • ora-23361 : materialized view "string" does not exist at master site
  • ora-02755 : osnfsmcre: cannot create chared memory file ?/dbs/ftt_.dbf
  • ora-10906 : Unable to extend segment after insert direct load
  • ora-30045 : No undo tablespace name specified
  • ora-25210 : invalid value for RELATIVE_MSGID, no message in queue with that msgid
  • ora-01225 : thread number string is greater than MAXINSTANCES string
  • ora-03249 : Uniform size for auto segment space managed tablespace should have atleast string blocks
  • ora-22878 : duplicate LOB partition or subpartition specified
  • ora-01179 : file string does not exist
  • ora-04083 : invalid trigger variable 'string'
  • ora-28110 : policy function or package string.string has error
  • ora-24013 : invalid value string, RETRY_DELAY should be non-negative
  • ora-29894 : base or varray datatype does not exist
  • ora-06815 : TLI Driver: could not link SPX and IPX streams
  • ora-23607 : invalid column "string"
  • ora-13227 : SDO_LEVEL values for the two index tables do not match
  • ora-39120 : Table string can't be truncated, data will be skipped. Failing error is: string
  • ora-14004 : missing PARTITION keyword
  • ora-22321 : method does not return any result
  • ora-23617 : Block string for script string has already been executed
  • ora-31509 : publication does not exist
  • ora-22978 : only simple attribute name is allowed in the WITH OBJECT OID clause
  • ora-14301 : table-level attributes must be specified before partition-level attributes
  • 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.