Archive log can not ship to GAP logfiles to standby DB automatically

Question

we have a non-real time standby database, which will receive the archive file from the primary database server most of the time, and will apply the logfiles only at one point of time daily.
Some times, we need to shutdown the Standby DB server for a while ( 3-4 hours).
The missed logfiles will catch up during the standby down time later.
But since last week we had an storage incident, the primary DB server stops to catch up the missed logfiles, and saw this message at the archvie trace file:
ABC: tkrsf_al_read: No mirror copies to re-read data
Current, we found the archive log gaps on the standby server, and have to manually copy those logfiles over and register them.
Saw some tips on the internet to change the parameter "log_archive_max_processes", but no help for us at all.
Here is the parameter on the Primary DB server:
log_archive_dest_2 = SERVICE=Standby_server reopen=300

Answer 1

which will receive the archive file from the primary database server most of the timeMost times from primary. Then remaining times? so you Copy manually and register?
Then it's dataguard not an manual standby.
Error 1034 received logging on to the standby
Errors in file /******/***arc210536.trc:
ORA-01034: ORACLE not available
FAL[server, ARC2]: FAL archive failed, see trace file.these errors in primary when , stanby is down and when primary tries to connect to standby, so tese errors not considerable to investigate ,
When you don't want to apply archives on standby no need to shutdown. Just put this value log_archive_dest_state_2='defer'
Once you enable check what are the errors in primary alert log file.
How is your network band width speed? Is it capable to hold that much archive data?
May be it will take some time when you pause & start.
Also use LGWR in log_archive_dest_2 for real time apply after creatin standby redo logs.
So post the alert log information once you enable standby database.