FAL does not seem to be starting to resolve gap
nshep1May 5 2010 — edited May 14 2010Hi -
I have 2 10.2.0.4 databases in a data guard config - with 1 phy standby.
This has been set up and running ok for a years.
Usually, when there is a log gap, I see in the alert log on the standby where it starts FAL to get the missign logs from the primary.
Currently there is a gap, and I am not seeing the standby even try to start fal, and so the logs are not applying of course.
Everything looks ok in alert logs, dgmgrl on both sides.
I tried restarting the stanby, and I see it go through the normal steps, ending with starting the managed apply, and usually right after that (after 5-10 min) I will see it start fal to try to get the missign logs.
It has been 1/2 a day and it just sits there.
The current logs on the primary are being sent ok (lgwr) to the standby ok.
Yesterday, I did tried to copy over a missing logs & register them to complete the gap - it applied it just fine and was back in sync.
But, it seems it will not stay in sync - as soon as a log gets missed (usually due to the wan network it seems) it just sits there - like it is now - no attempt by fal to get the missing logs.
Any ideas ?
Thanks in advance!