Manually process the v $ archive_gap method under DG, dgarchive_gap

Manually process the v $ archive_gap method under DG, dgarchive_gap

After 9i, the oracle slave uard standby database generally does not need to manually process the lost logs. FAL will automatically help us with the loss. The following example shows how to manually process the lost logs:

1. What logs are lost in the standby database and are not applied to the standby database?

SQL> select * from V $ ARCHIVE_GAP;

THREAD # LOW_SEQUENCE # HIGH_SEQUENCE #
-------------------------------------
1 9873 9876

We can see that the four archive logs from 9873 to 9876 are lost,

2. We found the four archive logs in the master database and sent them to the archive directory of the slave database;

3. register the slave Database

Alter database register logfile '/oracle/app/oracle/archive/4249873_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/4109875_629923600.arc ';

System alerted

Alter database register logfile '/oracle/app/oracle/archive/1_9876_629923600.arc ';

System alerted

4. Check the database logs to see if the logs are applied.

Thu Apr 8 15:55:17 2010
Media Recovery Log/oracle/app/oracle/archive/4249873_629923600.arc
Media Recovery Log/oracle/app/oracle/archive/4109874_629923600.arc
Media Recovery Log/oracle/app/oracle/archive/4249875_629923600.arc
Media Recovery Log/oracle/app/oracle/archive/4249876_629923600.arc

Or query the view.

V $ archived_log applied field

5. Check whether the standby database has a log GAP.

SQL> select * from V $ ARCHIVE_GAP;

If no row is selected, the archive log is not lost.

 

-- This article