Methods of manually processing log v$archive_gap in ORACLE dataguard _oracle

Since 9i, Oracle Dataguard generally do not need to manually process the lost log, FAL will automatically help us deal with, the following case by hand to handle the Lost log method:

1. What logs are missing from the standby query and not applied to the repository

 Sql> select * from V$archive_gap;
  thread# low_sequence# high_sequence#
-------------------------------------
     1     9873    9876

We can see 9873 to 9876 of these four archived logs lost,

2. We locate the four archive logs in the main library and send them to the Repository archive directory;

3. Reserve Library Registration

ALTER DATABASE register logfile '/ORACLE/APP/ORACLE/ARCHIVE/1_9873_629923600.ARC ';
System alerted
ALTER DATABASE register logfile '/ORACLE/APP/ORACLE/ARCHIVE/1_9874_629923600.ARC ';
System alerted
ALTER DATABASE register logfile '/ORACLE/APP/ORACLE/ARCHIVE/1_9875_629923600.ARC ';
System alerted
ALTER DATABASE register logfile '/ORACLE/APP/ORACLE/ARCHIVE/1_9876_629923600.ARC ';
System alerted

4. Check the database log to see if the application

Thu APR 8 15:55:17
Media Recovery log/oracle/app/oracle/archive/1_9873_629923600.arc
media Recovery Log/ Oracle/app/oracle/archive/1_9874_629923600.arc
Media Recovery log/oracle/app/oracle/archive/1_9875_ 629923600.arc
Media Recovery Log/oracle/app/oracle/archive/1_9876_629923600.arc

or query view

Applied field for V$archived_log

5, check whether there is still log gap

Sql> select * from V$archive_gap;

There is no row selection, which means there is no problem with the archive log loss.