MRP0: Background Media Recovery terminated with error 1274

MRP0: Background Media Recovery terminated with error 1274 [ID 739618.1]

Applies to:

Oracle Server - Enterprise Edition - Version: 9.2.0.8 to 11.2.0.2 - Release: 9.2 to 11.2
Information in this document applies to any platform.

Symptoms

Adding a Tablepace / Datafile in Primary Database causes the MRP in Physical Standby Database to terminate with the Error below. STANDBY_FILE_MANAGEMENT = MANUAL is set on the Standby Database.

MRP0: Background Media Recovery terminated with error 1274
ORA-01274: cannot add datafile '...dbf' - file could not be created 

In Unix Environment you will get the below Message when try to restart the MRP

ORA-01111: name for data file 163 is unknown - rename to correct file 

Cause

 
This Error occurs if we add a Datafile OR Tablespace in PRIMARY Database and that could not be translated to the Standby Database due to these Reasons:

* Standy_file_management is set to MANUAL 
* Primary & Physical Standby are having different file structures and DB_FILE_NAME_CONVERT is not set according to the Directory Structures in Primary and Standby 

The Redo Log generated from Primary will have Information about the Tablespace / Datafile added however it could not be created successfully in Physical Standby Database due to the standby_file_management = MANUAL
or is not able to find the specified Folder due to a missing / incorrect Filename Conversion. 
The File Entry is added to Standby Controlfile as "UNNAMED0000n" in /dbs or /database 
folder depends on the Operating System and eventually the MRP terminates. 



Alert Log in Standby Shows MRP is terminated with below error 
================================================================= 
File #5 added to control file as 'UNNAMED00005' because 
the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL 
The file should be manually created to continue. 
MRP0: Background Media Recovery terminated with error 1274 
Thu Sep 25 19:02:35 2008 
Errors in file c:\oracle\product\10.2.0\admin\mystd\bdump\mystd_mrp0_3436.trc: 
ORA-01274: cannot add datafile 'D:\ORADATA\PRIM\SALES01.DBF' - file could not be created 



By default it is AUTO by broker.

Solution

Perform all mentioned Steps on the Standby Database:

Step 1: Ensure the standby_file_management = 'MANUAL'

NOTE : For the parameter db_file_name_convert change if broker is enabled then edit the parameters using broker,

DGMGRL>edit database '<standby>' set property DbFileNameConvert='<>','<>';
DGMGRL>edit database '<standby>' set property StandbyFileManagement=manual;

By default StandbyFileManagement is AUTO by broker.

Step 2: Identify the File which is "unnamedn" 

SQL> select name from v$datafile;

NAME 
-------------------------------------------------------------------------------- 
D:\ORADATA\MYSTD\SYSTEM.DBF 
D:\ORADATA\MYSTD\UNDO.DBF 
D:\ORADATA\MYSTD\SYSAUX.DBF 
D:\ORADATA\MYSTD\SERVICE01.DBF 
C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\UNNAMED00005 



Step 3: Rename/create the Datafile to the correct Filename 

SQL> alter database create datafile 'C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\UNNAMED00005' as 'D:\oradata\mystd\sales01.dbf'; 

If the standby is in ASM + OMF then use the below command, 

SQL> alter database create datafile '/oracle/product/GSIPRDGB/dbs/UNNAMED00210' as <'+ASMDISKGROUPNAME'> size <specify the size of datafile>; 

or 

SQL>alter database create datafile '/oracle/product/GSIPRDGB/dbs/UNNAMED00210' as new;

Step 4: Verify the Filename is correct 

SQL> select name from v$datafile; 

NAME 
-------------------------------------------------------------------------------- 
D:\ORADATA\MYSTD\SYSTEM.DBF 
D:\ORADATA\MYSTD\UNDO.DBF 
D:\ORADATA\MYSTD\SYSAUX.DBF 
D:\ORADATA\MYSTD\SERVICE01.DBF 
D:\ORADATA\MYSTD\SALES01.DBF 


Step 5: Change the STANDBY_FILE_MANAGMENT to AUTO 

SQL> ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO scope=both; 

Step 6: Start the MRP (this is using Real Time Apply)

SQL> alter database recover managed standby database using current logfile disconnect; 

Database altered. 


Step 7: Verify the MRP is running as expected 

SQL> select process, status , sequence# from v$managed_standby; 

PROCESS STATUS SEQUENCE# 
--------- ------------ ---------- 
ARCH CLOSING 99 
ARCH CLOSING 103 
MRP0 APPLYING_LOG 104 
RFS IDLE 0 
RFS IDLE 0 
RFS IDLE 104