ORA-01244: unnamed datafile(s) added to control file by media recovery

Hi friends, in this article we are going to solve the ORA-01244 error, that you will be facing during manual database recovery.

ORA-01244 unnamed datafiles added to control file by media recovery

Cause: Actually that error most of the time you will face during the recovery, due to the datafile entry is not in the controlfile.

Suppose you maintaining the manual DR (standby database) and you added one data file on your production database but not added on the DR site, so when applying the archives on your DR site you will be facing an ORA-01244 error.

Actually, the datafile was added but the file name UNNAMEDnnnn, where nnnn is the file number, so using this unnamed file name with the location we create the datafile.

Action: Rename the file with the valid file name and restart the recovery. If the file still shows an error make it offline.

ORA-01654: unable to extend index solution

You will find out below error in the database alert log:

Errors in file /u01/app/11.2.0.3/diag/rdbms/ocp/ocp/trace/ocp_db_17085.trc:

ORA-00283: recovery session canceled due to errors
ORA-01244: unnamed datafile(s) added to control file by media recovery
ORA-01110: data file 21: ‘/u01/datafile/data/users021.dbf’
Slave exiting with ORA-283 exception

And your database recovery will abort.

How to Check missing data files on Standby

Execute the below queries to find the details of the file.

select * from v$recover_file where error like '%FILE%';
select file#, error, name from v$datafile_header where ERROR='FILE MISSING';
select file#, name from v$datafile where file#=??;

Using the below commands you can solve this error.

You maintain a manual standby and you recover it through applying archives from the source database.

Solution ORA-01244

To overcome this issue, you simply have to execute the below command.

SQL> alter database create datafile 21 (file# from error) as ‘/u01/app/oracle/datafile/users21.dbf’;

The path is where you want the data file to be created. This can be similar to the one reported in error (if you have the same path as the source) or could be different, as in this case.

Now, you can start your recovery.

ora-00283 ora-01244 ora-01110