Wednesday, January 19, 2011

FAL_CLIENT and FAL_SERVER Parameters

FAL (Fetch Archive Log) ===>>

Under certain circumstances, either because of network failures or a
busy source environment, a gap builds up between the target sending the
information and the destination receiving the changes and applying them.
Since the MRP/LSP process has no direct communication link with the primary
database to obtain a copy of the missing archive files, such gaps or
archive gaps are resolved by the fetch archive log (FAL) client and server,
identified by the initialization parameters FAL_CLIENT and FAL_SERVER.



FAL_SERVER specifies the FAL (fetch archive log) server for a standby database.
The value is an Oracle Net service name, which is assumed to be configured properly on the standby database system to point to the desired FAL server.

FAL_CLIENT specifies the FAL (fetch archive log) client name that is used by the FAL service, configured through the FAL_SERVER parameter, to refer to the FAL client. The value is an Oracle Net service name, which is assumed to be configured properly on the FAL server system to point to the FAL client (standby database). Given the dependency of FAL_CLIENT on FAL_SERVER, the two parameters should be configured or changed at the same time.




FAL_CLIENT and FAL_SERVER are initialization parameters used to configure log gap detection and resolution at the standby database side of a physical database configuration. This functionality is provided by log apply services
and is used by the physical standby database to manage the detection and resolution of archived redo logs.


FAL_CLIENT and FAL_SERVER only need to be defined in the initialization parameter file for the standby database(s). It is possible; however, to define these two parameters in the initialization parameter for the primary database server to ease the amount of work that would need to be performed if the primary database were
required to transition its role.

FAL_CLIENT specifies the TNS network services name for the standby database (which is sent to the FAL server process by log apply services) that should be used by the FAL server process to connect to the standby database.
The syntax would be:

FAL_CLIENT=

FAL_SERVER specifies the TNS network service name that the standby database should use to connect to the FAL server process.
The syntax would be:

FAL_SERVER=

Taken from http://www.idevelopment.info/data/Oracle/DBA_tips/Data_Guard_9i/DG_75.shtml#Using%20FAL_CLIENT%20and%20FAL_SERVER

In other words ,where my primary server is Afini and standby is stbyaf

Then for STBYAF

Fal_client=stbyaf

Fal_Server=Afini

And for Afini

Fal_client=afini

Fal_Server=stbyaf

Que is to always say it as it while assuming database is acting as standby.

No comments:

Post a Comment