Create control file

Open the database normally or resetlog depend upon the Redo log file you lost or have it. Create temp file as needed. Database is started upto no mount stage but during mount it will generate errors: Both errors are of different Server: ORA internal error code, arguments: [], [9], [8], [], [], [], [], [], [], [], [], [] ORA error in identifying control file, check alert log for more info Solution We decided to create an new control file for fixing the errors getting in startup the database.

DBF' ; 2. DBF' ; Control file created. Like this: Like Loading Follow Following. Smart way of Technology Join other followers. If compatibility is If compatibility is set to However, with compatibility set earlier than The following statement creates a new control file for the prod database a database that formerly used a different database name :.

Omitting a filename can cause loss of the data in that file, or loss of access to the entire database. Use caution when issuing this statement and be sure to follow the instructions in "Steps for Creating New Control Files". If you follow recommendations for control file backups as discussed in "Backing Up Control Files" , you will already have a list of datafiles and redo log files that reflect the current structure of the database.

However, if you have no such list, executing the following statements will produce one. If you have no such lists and your control file has been damaged so that the database cannot be opened, try to locate all of the datafiles and redo log files that constitute the database.

Any files not specified in step 5 are not recoverable once a new control file has been created. Moreover, if you omit any of the files that make up the SYSTEM tablespace, you might not be able to recover the database. If the database is open, shut down the database normally if possible.

In this case, you will need to recover from the loss of the redo logs step 8. Store a backup of the new control file on an offline storage device. See "Backing Up Control Files" for instructions for creating a backup. Loss or corruption of the control file requires a database recovery. The control file is read at the mount stage of database startup and is required for the database to be functional. Each control file is linked to a single database. Before the database is opened, Oracle reads the control file to determine whether the database is in a valid state to use.

The control file is updated almost continuously by the Oracle server when the database is in use and therefore must be available for write processing whenever the database is open. The control file is very important to the database. Some information is stored only in the control file rather than the data dictionary. The metadata includes flashback logs, block change tracking, RMAN backups, and datafile locations.

Often there are workarounds or solutions available and the control file does not need to be recreated at all. If you really must recreate the control file, or when instructed by Oracle, consider the following…. If all of the datafiles are not on disk in the first place, you will not able able to recreate the controlfile. If the datafiles are on disk, ensure that there are no offlined datafiles:.

Otherwise, once the control file is recreated with resetlogs all offlined datafiles cannot be added back to the database.