MRP0: Background Media Recovery terminated with error 1111

ISSUE:

Sun Jul 09 05:37:05 2017
Errors in file /oracleSID/SID/saptrace/diag/rdbms/SIDstnd/SID/trace/SID_pr00_4496.trc:
ORA-19502: write error on file "/oracleSID/SID/sapdata2/undo_31/undo.data31", block number 434688 (block size=8192)
ORA-27061: waiting for async I/Os failed
Linux-x86_64 Error: 28: No space left on device
Additional information: -1
Additional information: 1048576
ORA-19502: write error on file "/oracleSID/SID/sapdata2/undo_31/undo.data31", block number 434432 (block size=8192)
ORA-27085: Message 27085 not found;  product=RDBMS; facility=ORA
Additional information: 528384
Additional information: 1048576
File #307 added to control file as 'UNNAMED00307'.
Originally created as:
'/oracleSID/SID/sapdata2/undo_31/undo.data31'
Recovery was unable to create the file as:
'/oracleSID/SID/sapdata2/undo_31/undo.data31'
MRP0: Background Media Recovery terminated with error 1274
Errors in file /oracleSID/SID/saptrace/diag/rdbms/SIDstnd/SID/trace/SID_pr00_4496.trc:
ORA-01274: cannot add datafile '/oracleSID/SID/sapdata2/undo_31/undo.data31' - file could not be created
Managed Standby Recovery not using Real Time Apply
Recovery interrupted!
Recovery stopped due to failure in applying recovery marker (opcode 17.30).
Sun Jul 09 06:59:19 2017
Managed Standby Recovery not using Real Time Apply
MRP0: Background Media Recovery terminated with error 1111
Errors in file /oracleSID/SID/saptrace/diag/rdbms/SIDstnd/SID/trace/SID_pr00_43081.trc:
ORA-01111: name for data file 307 is unknown - rename to correct file
ORA-01110: data file 307: '/oracleSID/SID/112_64/dbs/UNNAMED00307'
ORA-01157: cannot identify/lock data file 307 - see DBWR trace file
ORA-01111: name for data file 307 is unknown - rename to correct file
ORA-01110: data file 307: '/oracleSID/SID/112_64/dbs/UNNAMED00307'
Recovery Slave PR00 previously exited with exception 1111
MRP0: Background Media Recovery process shutdown (SID)

Solution:

First check for the parameter standby_file_management on Standby:

standby@SQL> show parameter stand

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
standby_archive_dest                 string      /oracleSID/SID/dupsaparch/SIDa
                                                 rch
standby_file_management              string      AUTO

Change the standby_file_management parameter from MANUAL to AUTO.

standby@SQL>ALTER SYSTEM SET standby_file_management='MANUAL' SCOPE=BOTH;

NOW on primary check for the filename of the file_id 307 for which the error has occured.

primary@SQL> select file_name from dba_data_files where file_id=307;

FILE_NAME
--------------------------------------------------------------------------------
/oracleSID/SID/sapdata2/undo_31/undo.data31

SQL>

Now rename the unnamed datafile on standby with this name.

standby@SQL>alter database create datafile '/oracleSID/SID/112_64/dbs/UNNAMED00307' as '/oracleSID/SID/sapdata2/undo_31/undo.data31';

And then run your standby recovery.

standby@SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE using current logfile DISCONNECT FROM SESSION;

IN Alert log after running standby recovery.

Sun Jul 09 07:05:42 2017
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE using current logfile DISCONNECT FROM SESSION
Attempt to start background Managed Standby Recovery process (SID)
Sun Jul 09 07:05:42 2017
MRP0 started with pid=34, OS id=59423
MRP0: Background Managed Standby Recovery process started (SID)
 started logmerger process
Sun Jul 09 07:05:47 2017
Managed Standby Recovery starting Real Time Apply
Parallel Media Recovery started with 72 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Log /oracleSID/SID/dupsaparch/SIDarch1_52793_935091150.dbf
Media Recovery Log /oracleSID/SID/dupsaparch/SIDarch1_52794_935091150.dbf

Also Do not forget to set standby_file_management to AUTO after renaming the datafile Else you may invite same kind of issue again.

standby@SQL>ALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH;

Best Wishes
Nikhil Kumar.