Cause : An error occurred during CREATE CONTROLFILE

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

See accompanying errors.

update : 26-06-2017


  • ora-07327 : smpdal: attempt to destroy pga when it was not mapped.
  • ora-12843 : pdml lock not held properly on the table
  • ora-35023 : (QFCHECK09) The analytic workspace and EIF file definitions of workspace object have incompatible partition definitions.
  • ora-27011 : skgfrd: cannot read from file opened for write
  • ora-29823 : object being analyzed is not a table
  • ora-16762 : invalid database state
  • ora-03286 : ALLOCATE EXTENT not valid for HASH CLUSTERS
  • ora-09831 : snyStartThread: failed to build the server port set.
  • ora-19336 : Missing XML root element
  • ora-00269 : specified log file is part of thread string not string
  • ora-36683 : (XSDPART21) Partition string dimensioned by more than one composite.
  • ora-25156 : old style outer join (+) cannot be used with ANSI joins
  • ora-10615 : Invalid tablespace type for temporary tablespace
  • ora-06301 : IPA: Cannot allocate driver context
  • ora-06774 : TLI Driver: error sending break mode
  • ora-07716 : sksachk: invalid device specification for ARCHIVE
  • ora-01105 : mount is incompatible with mounts by other instances
  • ora-06927 : CMX: T_DATAIN received before all data written
  • ora-31447 : cannot create change tables in the SYS schema
  • ora-06737 : TLI Driver: connection failed
  • ora-02150 : invalid new tablespace name
  • ora-09767 : osnmfs: bad return code from msg_send.
  • ora-01578 : ORACLE data block corrupted (file # string, block # string)
  • ora-26723 : user "string" requires the role "string"
  • ora-38442 : The ADT "string" is not in a valid state.
  • ora-00289 : suggestion : string
  • ora-28151 : more than one user name specified for command
  • ora-08111 : a partitioned index may not be coalesced as a whole
  • ora-10918 : TABLESPACE GROUP name cannot be the same as tablespace name
  • ora-07403 : sfanfy: db_writers parameter not valid.
  • 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.