Issue with Dataguard:Failed to request gap sequence

[#1]

Hello Gurus,

We are facing an issue with our Dataguard node.

Archive logs are getting shipped from Primary node to Dataguard correctly.

But due to some issue, the logs ar enot getting applied on Dataguard.

Querying of the v$archive_gap showed that log files 69918 & 69919 were not appplied.

Dataguard node alert_sid.log :

-

---

Media Recovery Waiting for thread 2 sequence 69918

Fetching gap sequence in thread 2, gap sequence 69918-69919

FAL[client]: Failed to request gap sequence

GAP - thread 2 sequence 69918-69919

DBID 1059364943 branch 756090934

FAL[client]: All defined FAL servers have been attempted.

-

---

Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter is defined to a value that is sufficiently large

enough to maintain adequate log switch information to resolve archivelog gaps.

-

---

Archive log gap is for 69918 and 69919.

CONTROL_FILE_RECORD_KEEP_TIME value is 30 days in Dataguard.(and these logs are not 30 days old.so i think there is no need to think of changing parameter value).

STANDBY_FILE_MANAGEMENT is set to AUTO in Dataguard

The missing log files were shipped to Dataguard and are present there (But ddnt get applied for some reason).

In Standby database last applied log is : 69917

In Primary Last archived is : 73419

There are lot of archive logs to be applied in Standby.(73419-69917).

MRP process status in Dataguard is: WAIT FOR GAP

Could you please let me know what needs to be done in order to re-start Log applying in Data guard node.

Thanks in Advance,

Sam

[stefan_koehler]

Hello Sam,

The missing log files were shipped to Dataguard and are present there (But ddnt get applied for some reason).

... in this case it seems like the archive log files are not present on the primary site anymore and they are not registered on standby site. We don't know anything about your configuration and how you backup / delete your archive logs.

A solution for your current situation is to manually register the two archive logs with the sequence number 69918 and 69919. The root cause for this issue needs to be investigated on your own.

Register the missing archive log files with the following command on standby site:

shell> sqlplus / as sysdba
SQL> alter database register logfile '<PATH_TO_ARC_FILE>';

Documentation: http://docs.oracle.com/cd/E11882_01/server.112/e26088/statements_1004.htm#i2186977

Regards

Stefan