FAL gap in Oracle Data Guard logs

The FAL gap problem of Oracle Data Guard logs is found in the OracleData Guard environment. A standby database has a problem and needs to be redone. Because the previously configured environment is good, you only need to back up the full database of the master database to the slave database. However, after the data file is restored, a gap log file is displayed in alert. log during media restoration. The RFS process continues to extract other archive log files from the master database. Alert. the message in the log file is as follows: TueApr 9 14:20:56 2013 MediaRecovery Log + LOGDG/servdg2/archivelog/2013_04_09/thread_1_seq_71989.3551.812298053 MediaRecovery Waiting for thread 2 sequence 68042 Fetchinggap sequence in thread 2, gap sequence 68042-68094 TueApr 9 14:20:58 2013 RFS [1]: Archived Log: '+ LOGDG/servdg2/archivelog/2013_04_09/thread_2_seq_68052.2968.812298059 'tueapr 9 14:21:31 2013 Fetchinggap sequenc E in thread 2, gap sequence 68042-68051 TueApr 9 14:22:06 2013 FAL [client]: failed to request gap sequence GAP-thread 2 sequence 68042-68051 DBID 3658273059 branch 717104091 FAL [client]: All defined FAL servers have been attempted. --------------------------------------------------------------- Check thatthe CONTROL_FILE_RECORD_KEEP_TIME initialization parameteris defined to a value that is sufficie Ntly large enough tomaintain adequate log switch information to resolve archiveloggaps. ----------------------------------------------------- the standby database cannot resume media recovery due to log interruption. Our problem is how to retrieve these log files. Determine the status of archived logs in the master database. Select * from v $ archived_log B where B. SEQUENCE # & gt; = 68042 and B. THREAD # = 2 andb. SEQUENCE # & lt; = 68051 and B. DEST_ID = 1 and B. DELETED = 'yes'; this SQL statement confirms that these archived logs have been DELETED. Archive log files are deleted on a regular basis through the RMAN tool. Because the restoration process is very long, the archive log has been backed up and removed after the restoration is complete. RMAN> list backup of archivelog from sequence 68042 until sequence 68051 thread 2; find the result set in the rman backup set and use restore archivelog to restore. RMAN> restore archivelog from sequence 68042 until sequence 68051 thread 2; in this way, the backup database can continue to obtain these archive log files. If no, the master database directs to the log_archive_dest_state _ * of the standby database before defer and enable the service. Because the master database is RAC, multiple instances will prompt this error and solve it in sequence.