Re: Use of FAL_SERVER

From: Nassyam Basha <nassyambasha_at_gmail.com>
Date: Sat, 23 Feb 2013 19:58:15 +0530
Message-ID: <CAABGLuLmQ8NFf1AjdeC-BP1K8Gre7+vpSfx0e7iKmZd+s9nF3Q_at_mail.gmail.com>



Purav,
Usually whenever you set Oracle net service name in LOG_ARCHIVE_DEST_n the archive/redo will be transported to the remote destinations, As you said from latest releases FAL parameters no longer required . In some situations may be because of network failures[possible network disconnect with primary] or due to some maintenance archives deferred from primary, If you have 100s or 1000s of archive GAPs, Then recovery processes[MRP] cannot fetch the archives because they do not have any communication with primary database.In such GAP's can be resolved only by FAL parameters. FAL parameters is a set of Oracle net service names that exist on the standby database which points to the primary databases and any of the standby databases. Hope this helps.

Thanks & Regards,
Nassyam Basha.
www.oracle-ckpt.com

On Sat, Feb 23, 2013 at 5:44 PM, Purav Chovatia <puravc_at_gmail.com> wrote:

> Hello Experts,
> What is the advantage or when is it required to set the FAL_Server and
> FAL_Client parameters?
>
> On a 10.2.0.4 DB with physical standby, gap detection and resolution
> happened (using automatic gap resolution) without setting FAL_server or
> FAL_Client on the primary or the standby. So I could not understand why
> should one be ever required to set the said params? Can somebody pls
> enlighten me?
>
> Thanks.
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

-- 
Thanks & Regards,
Nassyam Basha.


--
http://www.freelists.org/webpage/oracle-l
Received on Sat Feb 23 2013 - 15:28:15 CET

Original text of this message