Problem:
Because of a network problem one of our physical standby database, there was some gaps.
...
9597 2 +ADATA/astb/archivelog/2015_11_09/thread_2_seq_9597.1827.895359343
9600 2 +ADATA/astb/archivelog/2015_11_09/thread_2_seq_9600.1828.895360629
9601 2 +ADATA/astb/archivelog/2015_11_09/thread_2_seq_9601.1831.895361495
9604 2 +ADATA/astb/archivelog/2015_11_09/thread_2_seq_9604.1825.895363191
9607 2 +ADATA/astb/archivelog/2015_11_10/thread_2_seq_9607.1824.895364061
9608 2 +ADATA/astb/archivelog/2015_11_10/thread_2_seq_9608.1823.895364505
9609 2 +ADATA/astb/archivelog/2015_11_10/thread_2_seq_9609.1826.895365409
...
After the network problem was solved by our system team, Standby RFS processes can succesfully get recent archived logs. But could not get earlier gap archived logs. Even not try to get them. We monitor this via V$MANAGED_STANDBY view.
When we try to restart media recovery on the standby site. We still see the following alertlog warnings.
