ORA-01178: file string created before last CREATE CONTROLFILE, cannot recreate

Cause : Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that existed at the last CREATE CONTROLFILE command. The information needed to recreate the file was lost with the control file that existed when the file was added to the database.

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

Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created.

update : 26-06-2017
ORA-01178

ORA-01178 - file string created before last CREATE CONTROLFILE, cannot recreate
ORA-01178 - file string created before last CREATE CONTROLFILE, cannot recreate

  • ora-14133 : ALTER TABLE MOVE cannot be combined with other operations
  • ora-28538 : result set not found
  • ora-06530 : Reference to uninitialized composite
  • ora-02730 : osnrnf: cannot find user logon directory
  • ora-24017 : cannot enable enqueue on QUEUE, string is an exception queue
  • ora-00723 : Initialization parameter COMPATIBLE must be explicitly set
  • ora-12004 : REFRESH FAST cannot be used for materialized view "string"."string"
  • ora-37138 : (XSCCOMP13) You cannot delete values from workspace object because it is an aggregated COMPRESSED COMPOSITE.
  • ora-13504 : No SYSAUX datafile clause specified
  • ora-30336 : no child for specified JOIN KEY
  • ora-29951 : warning in the execution of ODCIINDEXSPLITPARTITION routine
  • ora-24386 : statement/server handle is in use when being freed
  • ora-12057 : materialized view "string"."string" is INVALID and must complete refresh
  • ora-14461 : cannot REUSE STORAGE on a temporary table TRUNCATE
  • ora-10259 : get error message text from remote using explicit call
  • ora-01859 : a non-alphabetic character was found where an alphabetic was expected
  • ora-14055 : keyword REBUILD in ALTER INDEX REBUILD must immediately follow
  • ora-28110 : policy function or package string.string has error
  • ora-29827 : keyword USING is missing
  • ora-32311 : materialized view definition query selects an unsupported user-defined type
  • ora-38732 : Expected file size string does not match string.
  • ora-01546 : tablespace contains active rollback segment 'string'
  • ora-16052 : DB_UNIQUE_NAME attribute is required
  • ora-31601 : Function string cannot be called now that fetch has begun.
  • ora-19232 : XQ0012 - imported schemas violate validity rules
  • ora-13374 : SDO_MBR not supported for geodetic data
  • ora-29551 : could not convert string to Unicode
  • ora-30132 : invalid key index supplied
  • ora-12164 : TNS:Sqlnet.fdf file not present
  • ora-06020 : NETASY: initialisation failure
  • 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.