Oracle Database 11g Enterprise Edition Release 220.127.116.11.0 - 64bit Production
Oracle dataguard: Primary & Physical standby only.
Certain archive logs were not copied from Primary database to Physical standby database. As there was no space, it was unable to copy them. After I cleared the space, standby started copying archivelogs from 2185.
Now, is there a way I can manually trigger the standby database to request missing logs from primary? Can some one please help. Thanks for your time!
(FYI: I am aware of copying archive logs manually from production to standby 2) restoring incremental production backup onto standby)
SQL> select * from v$archive_gap;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
---------- ------------- --------------
1 2102 2184
I would give the Standby some time to correct before I started copying logs. Stop and start MRP on the standby and see if it does not recover on tis own first. I have had Standby's down for 50 hours and been behind 200 logs and they have alway recovered without me having to manually do anything.
Try this query from the primary side and post the results:
If you have to do it manually the register command is like this example:
ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/oradata/STANDBY/archive/PRIMARY_1_20_716110538.arc';
I agree with msberg and also shutting down and restarting standby database(which will stop MRP and other processes ) will fix the problem but ONLY if its possible to take standby down.
mseberg: The only reason I am saying because sometime system behaves weird and just by stopping MRP doesn't start the recovery. This happened with me.
You can try to disable and then enable the second log destination (alter system set log_archive_dest_state_2=defer; and then enable). Also you switch logfile on the primary (alter system switch logfile;) you should see in few seconds the log is shipped on the standby. Right after that the standby should try to apply the log and if there is a GAP it will try automatically to obtain all the missing logs from the FAL server. Also make sure the recovery process is started on your standby. To avoid deleting any arcihvelog by mistake consider setting archivelog deletion policy.
As others have said, as long as the archivelogs are still available on the primary, the standby should start copying them in a few minutes. If it doesn't, that means FAL services isn't working and you need to fix it. There's a bug that can cause the archive processes to lock up on the primary under certain conditions. Doc ID 1130523.1 in Metalink will tell you what to do about it.