MRP: Background Media Recovery process shutdown on Physical standby Dataguard

-

MRP: Background Media Recovery process shutdown on Physical standby Dataguard

Applies to: 
Oracle Database 10gR2

Description:
RFS process successfully running, archive logs successfully shipped from Primary server to standby, but archive logs did not apply. MRP process going to shutdown automatically. After doing some research work I found the following solution:

Solution:
SQL> alter database recover managed standby database cancel;
SQL> alter database recover managed standby database cancel;
alter database recover managed standby database cancel
*
ERROR at line 1:
ORA-16136: Managed Standby Recovery not active

SQL> alter database recover managed standby database disconnect from session;

Alert log:
alter database recover managed standby database disconnect from session
Sat Jun  9 09:51:56 2012
Attempt to start background Managed Standby Recovery process (PROD)
MRP0 started with pid=18, OS id=6591
Sat Jun  9 09:51:56 2012
MRP0: Background Managed Standby Recovery process started (PROD)
Managed Standby Recovery not using Real Time Apply
MRP0: Background Media Recovery terminated with error 1111
Sat Jun  9 09:52:01 2012
Errors in file /d01/oracle/proddb/10.2.0/admin/PROD_pebsdbdrrt/bdump/prod_mrp0_6591.trc:
ORA-01111: name for data file 59 is unknown - rename to correct file
ORA-01110: data file 59: '/d01/oracle/proddb/10.2.0/dbs/UNNAMED00059'
ORA-01157: cannot identify/lock data file 59 - see DBWR trace file
ORA-01111: name for data file 59 is unknown - rename to correct file
ORA-01110: data file 59: '/d01/oracle/proddb/10.2.0/dbs/UNNAMED00059'
Sat Jun  9 09:52:01 2012
Errors in file /d01/oracle/proddb/10.2.0/admin/PROD_pebsdbdrrt/bdump/prod_mrp0_6591.trc:
ORA-01111: name for data file 59 is unknown - rename to correct file
ORA-01110: data file 59: '/d01/oracle/proddb/10.2.0/dbs/UNNAMED00059'
ORA-01157: cannot identify/lock data file 59 - see DBWR trace file
ORA-01111: name for data file 59 is unknown - rename to correct file
ORA-01110: data file 59: '/d01/oracle/proddb/10.2.0/dbs/UNNAMED00059'
Sat Jun  9 09:52:01 2012
MRP0: Background Media Recovery process shutdown (PROD)
Sat Jun  9 09:52:02 2012
Completed: alter database recover managed standby database disconnect from session

SQL> select thread#,max(sequence#) from v$log_history group by thread#;
   THREAD# MAX(SEQUENCE#)
---------- --------------
248980

SQL> select severity, error_code,message,to_char(timestamp,'DD-MON-YYYY HH24:MI:SS') from v$dataguard_status;

SQL> archive log list

SQL> ho ls -ltra /archive/logs/

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

PROCESS   STATUS        SEQUENCE#
--------- ------------ ----------
ARCH      CONNECTED             0
ARCH      CONNECTED             0
RFS       IDLE                  0
RFS       IDLE                  0

SQL> ho ps -ef|grep mrp
oracle   30350 30330  0 09:24 pts/2    00:00:00 /bin/bash -c ps -ef|grep mrp
oracle   30352 30350  0 09:24 pts/2    00:00:00 grep mrp

SQL> select file#,name from v$datafile where name like '%UNNAMED%';
     FILE#
----------
NAME
--------------------------------------------------------------------------------
        59
/d01/oracle/proddb/10.2.0/dbs/UNNAMED00059
SQL> alter database create datafile '/d01/oracle/proddb/10.2.0/dbs/UNNAMED00059' AS '/data3/proddata/daw_INV_06.dbf';

SQL> alter database recover managed standby database cancel;
alter database recover managed standby database cancel
*
ERROR at line 1:
ORA-16136: Managed Standby Recovery not active

SQL> alter database recover managed standby database disconnect from session;

Database altered.

SQL> select thread#,max(sequence#) from v$log_history group by thread#;

   THREAD# MAX(SEQUENCE#)
---------- --------------
         1         248980
SQL> /

   THREAD# MAX(SEQUENCE#)
---------- --------------
         1         248981


Problem has been resolved, now MRP process started and recovering the archive logs.

Your comments, especially which will help us improve the functionality, will be greatly appreciated :)

Comments

  1. AnonymousOctober 4, 2012 at 12:20:00 PM GMT+5

    Really helpful!!

    ReplyDelete
  2. AnonymousJuly 20, 2013 at 9:41:00 PM GMT+5

    from where you got the name 'data3/proddata/daw_INV_06.dbf' to recreate the datafile 59

    ReplyDelete
  3. Rana Abdul WahidJuly 22, 2013 at 10:00:00 AM GMT+5

    Hi,

    Actual name of data file# 59 is 'data3/proddata/daw_INV_06.dbf' as on primary server you can check.

    After corruption it create the temporary datafile as '/d01/oracle/proddb/10.2.0/dbs/UNNAMED00059'

    Thanks
    Rana

    ReplyDelete
  4. AnonymousJune 26, 2014 at 12:33:00 AM GMT+5

    This really helped. I have real-time apply set and I didn't have to bring the datagaurd instance down to fix it. I just wanted to add how I found out which datafile it was. I'm sure others already know but if not this is what I did: PRIMARY DB
    SQL>select file#,name from v$datafile where file#=xxx; (number you get from the unnamed sql) this will help when you do the alter database create datafile.

    ReplyDelete

Post a Comment

Popular posts from this blog

How to Rebuild/Recreate Concurrent Manager

-
How to Rebuild/Recreate Concurrent Manager Applies to:             Oracle Applications – Version: 11.5.10.2 and above Description:             After cloning, concurrent manager unable to start successfully at 0 status. Solution:             Check the following solution on test environment before implement on production environment, rebuild concurrent manager using following steps: ·          Stop concurrent manager and wait to clear all processes of FNDLIBR or kill the processes ·          select * from fnd_concurrent_processes where process_status_code='A'; ·          update fnd_concurrent_processes set process_status_code='K' where process_status_code='A'; ·          select * from fnd_concurrent_queues where control_code='N'; ·          update fnd_concurrent_queues set control_code=null where control_code='N'; ·          update fnd_concurrent_queues set node_name=null,node_name2=null where concur
Read more

FRM-92101: Forms Server Not Starting Up

-
Forms Server Not Starting Up / Forms Server Start Up Issue Applies to:             Oracle Enterprise Linux – Version: 5             Oracle EBS R12 Description:             After cloning EBS R12 successfully on a new server machine, when I am going to access any form on EBS clone it did not open the page and show the following error: FRM-92101: Forms Server Java Exception: oracle.forms.net.ConnectionException: Forms session <1> failed during startup: no response from runtime process at oracle.forms.net.ConnectionException.createConnectionException(Unknown Source) at oracle.forms.net.HTTPNStream.getResponse(Unknown Source) I have restarted all the services of application and database but the problem is same. I have also restarted the whole machine/server but still the same issue. Cause and Solution: I found the following error: In $LOG_HOME/ora/10.1.3/j2ee/<oacore>/<oacore>_<default_group_1>/application.log $LOG_HOME/ora/1
Read more

ORA-10564 Tablespace UNDOTBS1 ORA-01110 ORA-10560

-
ORA-10564 Tablespace UNDOTBS1 ORA-01110 ORA-10560 Applies to:             Oracle Enterprise Linux – Version: 7             Oracle EBS R12 Description:             After abnormal shutdown of server we face the problem “ORA-10564 Tablespace UNDOTBS1 ORA-01110 data file 7 UNDOTBS01.DBF ORA-10560 block type KTU UNDO BLOCK”. I have restarted all the services of database but the problem is same. I have also restarted the whole machine/server but still the same issue. Solution:             After some research I found that recreate the undo tablespace to resolve the issue. Following the steps to resolve the above issue: 1-       Connect / as sysdba 2-       Create undo tablespace UNDOTBS2 datafile ‘/u01/oracle/oradata/undotbs02.dbf’ size=1G; 3-       Alter system set undo_tablespace = UNDOTBS2; 4-       Shutdown immediate 5-       startup 6-       Drop tablespace UNDOTBS1 including contents and datafiles; Database is working fine now.
Read more