Registered Archived REDO Log Will No Longer Ship -- Causing GAP
edited Mar 20, 2012 4:49PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered
Hi. I was having a network issue where partial redo logs were shipping to my physical standby. Managed recovery deleted the partial logs immedaitely. Two of these logs got registered
select sequence#, first_time, next_time, applied from v$archived_log order by sequence#;
....
16401 Mar 06 2012 12:15:46 Mar 06 2012 12:56:54 NO
16401 Mar 06 2012 12:15:46 Mar 06 2012 12:56:54 NO
So now the managed recovery process thinks that I have these logs on disk and it will no longer pull the log #16401 from the standby database. RFS is transferring all the later logs that are required, but I now have a gap because RFS won't pull log #16401.
When I try to start managed recovery to apply it quits right away because it can't find this log. Any thoughts on how I can tell oracle to pull this file from the standby?
0