MRP process not start in standby / Archive log not applying in standby Database

Applies to:

 Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.
***Checked for relevance on 31-Aug-2012***
***Checked for relevance on 5-Aug-2014*** 

Symptoms

Physical standby recovery reports error in alert log:

Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Log /back/flash_recovery_area/STLBAST/archivelog/1_28158_842022897.arc
Errors in file /u01/app/oracle/diag/rdbms/stlbast/STLBAST/trace/STLBAST_pr00_27378.trc  (incident=640459):
ORA-00600: internal error code, arguments: [2619], [28158], [], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/stlbast/STLBAST/incident/incdir_640459/STLBAST_pr00_27378_i640459.trc
Sun Oct 19 16:40:53 2014
Completed:  alter database recover managed standby database disconnect from session
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors with log /back/flash_recovery_area/STLBAST/archivelog/1_28158_842022897.arc
MRP0: Background Media Recovery terminated with error 600
Errors in file /u01/app/oracle/diag/rdbms/stlbast/STLBAST/trace/STLBAST_pr00_27378.trc:
ORA-00600: internal error code, arguments: [2619], [28158], [], [], [], [], [], [], [], [], [], []
Recovery interrupted!
Errors in file /u01/app/oracle/diag/rdbms/stlbast/STLBAST/trace/STLBAST_pr00_27378.trc:
ORA-00600: internal error code, arguments: [2619], [28158], [], [], [], [], [], [], [], [], [], []
Slave exiting with ORA-600 exception
Errors in file /u01/app/oracle/diag/rdbms/stlbast/STLBAST/trace/STLBAST_pr00_27378.trc:
ORA-00600: internal error code, arguments: [2619], [28158], [], [], [], [], [], [], [], [], [], []
Sun Oct 19 16:40:53 2014
Dumping diagnostic data in directory=[cdmp_20141019164053], requested by (instance=1, osid=27378 (PR00)), summary=[incident=640459].
Errors in file /u01/app/oracle/diag/rdbms/stlbast/STLBAST/trace/STLBAST_mrp0_27376.trc  (incident=640451):
ORA-00600: internal error code, arguments: [2619], [28158], [], [], [], [], [], [], [], [], [], []

Cause

ORA-600[2619] is raised due to an invalid next_change# detected in archive log.

In this case, it is caused by the archive log disk space ran out on standby site, causing that archive log not fully written on disk. This lead to ORA-600[2619] when the archive log was applied.

Per standby alert log:



Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Log /back/flash_recovery_area/STLBAST/archivelog/1_28158_842022897.arc
Errors in file /u01/app/oracle/diag/rdbms/stlbast/STLBAST/trace/STLBAST_pr00_27378.trc  (incident=640459):
ORA-00600: internal error code, arguments: [2619], [28158], [], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/stlbast/STLBAST/incident/incdir_640459/STLBAST_pr00_27378_i640459.trc

Solution

1. Clear the disk space where archive log stored on standby site

2. Copy the problem archive log (eg: 1_28158_842022897.arc) from the primary site and replace the one on the standby, then restart Managed Recovery.

Archive log should be applied properly now


SQL> alter database recover managed standby database cancel;  --- Cancel first

Database altered.

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;

Database altered.

SQL>

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;