Data Guard

How to Resolve ORA-01579 in MRP

ORA-01579 in MRP

After shrinking (i.e. resizing) a data file successfully, I was worry about the applying state of the standby database. Not surprisingly, I found ORA-01579: write error occurred during recovery in Managed Recovery Process (MRP) log.

oracle@boston>tail -f orcl_mrp0_23309410.trc
...
*** 2019-03-15 08:51:13.521
Media Recovery Log /oradata/ORCL/ARCH/ORCL_1_342376.arc
*** 2019-03-15 09:02:01.230
Media Recovery Log /oradata/ORCL/ARCH/ORCL_1_342377.arc
Background Media Recovery terminated with error 1579
ORA-01579: write error occurred during recovery
----- Redo read statistics for thread 1 -----
Read rate (ASYNC): 392348293Kb in 1266511.01s => 0.30 Mb/sec
Longest record: 123Kb, moves: 359779/1303018031 (0%)
Change moves: 550581746/2311816853 (1%), moved: 136648Mb
----------------------------------------------
*** 2019-03-15 09:02:58.109
Managed Recovery: Not Active posted.
Background Media Recovery process shutdown
*** 2019-03-15 09:02:58.117

Restart MRP

The MRP was dead in the middle of an archived log 342377. Next, I tried to start up MRP manually.

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

Database altered.

Then we checked MRP log. Since new MRP was running on a new process, you had to know where the trace file is.

oracle@boston>ls -ltr | tail -2
-rw-r-----   1 oracle   oinstall        541 Mar 15 09:08 orcl_mrp0_20706230.trc
-rw-r--r--   1 oracle   oinstall   10228732 Mar 15 09:08 alert_ORCL.log
oracle@boston>tail -f orcl_mrp0_20706230.trc
...
*** 2019-03-15 09:06:55.990
Managed Recovery: Active posted.
Media Recovery Log /oradata/ORCL/ARCH/ORCL_1_342377.arc
*** 2019-03-15 09:08:41.606
Media Recovery Log /oradata/ORCL/ARCH/ORCL_1_342378.arc

As we can see in the log, it survived through archived log 342377 and subsequent 342378.

I thought I was going to copy the data file from the primary to the standby database. Just like the way I did in resolving ORA-00600 [3020] on the standby. I think I was lucky.

Leave a Reply

Your email address will not be published. Required fields are marked *