ORA-00328 ORA-00334 mrp0: background media recovery terminated with error 328

Environment Introduction: a two-node single-instance Linux + oracle11.2.0.3 + customized uard maximize availability environment was set up a few days ago.

Fault description: synchronization failed today. An error message is found in the trace file alert_orcl.log, but the MRP cannot be started.

Mrp0: background media recovery terminated with error 328

ORA-00328: 8386238,897 2415
ORA-00334: '/opt/Oracle/fast_recovery_area/dg_bei/archivelog/2014_09_28/o1_mf_1_830_b2h9mjmn _. arc'

The trace file alert_orcl.log reports a network disconnection error with the master database before the preceding error is reported.

RFS [4]: assigned to RFS process 20669
RFS [4]: Possible network disconnect with primary database
Sun Sep 28 13:23:48 2014

 

Mrp0: background media recovery terminated with error 328The detailed error message is as follows:

Mon Sep 29 14:32:28 2014
Alter database recover managed standby database using current logfile disconnect from session nodelay
Attempt to start background managed Standby Recovery Process (orcl)
Mon Sep 29 14:32:28 2014
Mrp0 started with PID = 27, OS id = 23710
Mrp0: Background managed standby recovery process started (orcl)
Started logmerger Process
Mon Sep 29 14:32:33 2014
Managed standby recovery starting real time apply
Parallel media recovery started with 2 slaves
Waiting for all non-current orls to be archived...
All non-current orls have been archived.
Clearing online redo logfile 1/opt/Oracle/oradata/orcl/redo01.log
Clearing online log 1 of thread 1 sequence number 835
Clearing online redo logfile 1 complete
Clearing online redo logfile 2/opt/Oracle/oradata/orcl/redo02.log
Clearing online log 2 of thread 1 sequence number 834
Clearing online redo logfile 2 complete
Clearing online redo logfile 3/opt/Oracle/oradata/orcl/redo03.log
Clearing online log 3 of thread 1 sequence number 835
Clearing online redo logfile 3 complete
Media recovery log/opt/Oracle/fast_recovery_area/dg_bei/archivelog/2014_09_28/o1_mf_1_830_b2h9mjmn _. Arc
Errors with log/opt/Oracle/fast_recovery_area/dg_bei/archivelog/2014_09_28/o1_mf_1_830_b2h9mjmn _. Arc
Mrp0: background media recovery terminated with error 328
Errors in file/opt/Oracle/diag/rdbms/dg_bei/orcl/Trace/orcl_pr00_23712.trc:
ORA-00328: 8386238,897 2415
ORA-00334: '/opt/Oracle/fast_recovery_area/dg_bei/archivelog/2014_09_28/o1_mf_1_830_b2h9mjmn _. arc'
Managed standby recovery not using real time apply
Recovery interrupted!
Completed: Alter database recover managed standby database using current logfile disconnect from session nodelay
Mrp0: background media recovery process Shutdown (orcl)
Mon Sep 29 14:34:06 2014
RFS [1]: assigned to RFS process 23726
RFS [1]: opened log for thread 1 sequence 836 dbid 1356850190 branch 829069458
Archived log entry 77 added for thread 1 sequence 836 RLC 829069458 ID 0x50df5e0e DEST 2:
Mon Sep 29 14:34:08 2014
Primary database is in maximum availability mode
Changing standby controlfile to resynchronization level
Standby controlfile consistent with primary
RFS [2]: assigned to RFS process 23728
RFS [2]: Selected log 4 for thread 1 sequence 838 dbid 1356850190 branch 829069458
Mon Sep 29 14:34:08 2014
RFS [3]: assigned to RFS process 23730
RFS [3]: Selected log 5 for thread 1 sequence 837 dbid 1356850190 branch 829069458
Mon Sep 29 14:34:08 2014
Archived log entry 78 added for thread 1 sequence 837 ID 0x50df5e0e DEST 1:
Changing standby controlfile to maximum availability level
RFS [2]: Selected log 5 for thread 1 sequence 839 dbid 1356850190 branch 829069458
Mon Sep 29 14:34:11 2014
Archived log entry 79 added for thread 1 sequence 838 ID 0x50df5e0e DEST 1:

 

Processing Process:

1. Check for recovery-related processes on the slave database. MRP is indeed missing.

Select process, status, sequence # from V $ managed_standby;

650) This. width = 650; "Title =" .jpg "alt =" wkiol1qpkn3bkrovaaczc41x_wu217.jpg "src =" http://s3.51cto.com/wyfs02/M02/4B/4B/wKioL1QpKN3BkrovAACZc41X_wU217.jpg "/>

 

2. Check the archive log view on the slave Database

SQL> select name, sequence #, applied from V $ archived_log;

Strange thing: the archive log reported in the trace log is displayed to be applied, as shown in the red box 650) This. width = 650; "Title =" qq 40929164432.jpg "alt =" wkiol1qphucx1wlqaaqvh2jnomw229.jpg "src =" http://s3.51cto.com/wyfs02/M02/4B/4A/wKioL1QpHUCx1WlqAAQvH2JNOMw229.jpg "/>

 

3. compare the archive logs of the master database and the slave database on February 28,. The data and size are different. The backup database has more logs than the master database, but is smaller than the master database, as shown in: (it is estimated that the size is inconsistent due to network interruption during log transmission)

650) This. width = 650; "Title =" master and backup warehouse conversion log .jpg "alt =" wkiom1qpjbrctkthaaqtnjihqnm433.jpg "src =" http://s3.51cto.com/wyfs02/M01/4B/49/wKiom1QpJbrCTKThAAQTnJiHqNM433.jpg "/>

 

4. the omnipotent Google search, probably because of an error in archiving log transmission. Copy the log from the master database to the slave database, and then perform restoration.

4.1 just in case, back up the archive log of the slave database 2014_09_28, and then delete the archive folder of the slave database 2014_09_28.

4.2 copy the archive folder 2014_09_28 from the master database to the slave Database

4.3 perform restoration on the slave Database

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

Check the trace log.

 

5. SQL> select name, sequence #, applied from V $ archived_log;

It shows that it can be used normally, but there is a log (shown in the red box) That is useless. I guess because the log files copied from the master database do not have this file (only five, the original slave database has 8), and the data is checked normally. The fault should be solved.

650) This. width = 650; "Title =" qq 40929174142.jpg "alt =" wkiol1qpke2ywgkqaapi6rhxiiw311.jpg "src =" http://s3.51cto.com/wyfs02/M01/4B/4C/wKioL1QpKe2yWgkQAAPI6rhxIIw311.jpg "/>

This article is from the "morning song muniu" blog, please be sure to keep this http://168ok8.blog.51cto.com/73394/1559515

ORA-00328 ORA-00334 mrp0: background media recovery terminated with error 328