ORA-600[2619] During Physical Standby Recovery

Issue:
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 4 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.

Media Recovery Log /swapphome/oracle/app/oradata/obieeproddb/archives/1_7011_876410455.dbf

Errors in file /swapphome/oracle/app/diag/rdbms/obieestbydb/obieestbydb/trace/obieestbydb_pr00_27961.trc:

ORA-00600: internal error code, arguments: [2619], [7011], [], [], [], [], [], [], [], [], [], []
Slave exiting with ORA-600 exception
Errors in file /swapphome/oracle/app/diag/rdbms/obieestbydb/obieestbydb/trace/obieestbydb_pr00_27961.trc:
ORA-00600: internal error code, arguments: [2619], [7011], [], [], [], [], [], [], [], [], [], []
Sun Aug 09 17:11:31 2015
Dumping diagnostic data in directory=[cdmp_20150809171131], requested by (instance=1, osid=27961 (PR00)), summary=[incident=6283].
Errors in file /swapphome/oracle/app/diag/rdbms/obieestbydb/obieestbydb/trace/obieestbydb_mrp0_27959.trc  (incident=6274):
ORA-00600: internal error code, arguments: [2619], [7011], [], [], [], [], [], [], [], [], [], []
ORA-10877: error signaled in parallel recovery slave
ORA-10877: error signaled in parallel recovery slave
ORA-10877: error signaled in parallel recovery slave
ORA-10877: error signaled in parallel recovery slave

Cause while applying the above log the mount point got 100% occupied no space left in the mount point.

RFS[11]: Opened log for thread 1 sequence 7009 dbid 912770197 branch 876410455

Non critical error ORA-48181 caught while writing to trace file "/swapphome/oracle/app/diag/rdbms/obieestbydb/obieestbydb/trace/obieestbydb_rfs_32359.trc"

Error message: Linux-x86_64 Error: 28: No space left on device

Additional information: 1

Writing to the above trace file is disabled for now on...

RFS[10]: Possible network disconnect with primary database

RFS[11]: Possible network disconnect with primary database

Solution:

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

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

Archive log should be applied properly now.