fbpx
en English
ar Arabiczh-CN Chinese (Simplified)nl Dutchen Englishfr Frenchde Germanit Italianpt Portugueseru Russianes Spanish

Why do we use FAL_SERVER and FAL_CLIENT parameters in Oracle dataguard

In this article, we are going to understand why we use FAL_SERVER and FAL_CLIENT parameters in the Oracle dataguard environment. FAL full form is “fetch archive log“.

The FAL is an oracle data guard environment parameter.

With the name, you can clearly understand it fetched the archive logs for the standby database from the primary database server using oracle net service.

Suppose due to network failure or any other reason there is a gap occurring between primary and standby. The FAL (Fetch Archive Log) will find those missing archivelog files which fulfill the gap between the primary and standby database. This is the work of fal_server and fal_client.

My tnsnames.ora file

In my case here are my tnsnames.ora file which has both primary and standby database entries.


OCPPR =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = PRIMARYSERVER)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ocppr)
)
)


OCPDR =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP) (HOST = STANDBYSEVRER)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ocpdr)
)
)

How to configure the FAL_SERVER and FAL_CLIENT parameter

Use the below commands to update fal-server and fal-client parameter values.

Primary side configuration

SQL>ALTER SYSTEM SET FAL_SERVER=OCPDR;
SQL>ALTER SYSTEM SET FAL_CLIENT=OCPPR;

Standby side configuration

SQL>ALTER SYSTEM SET FAL_SERVER=OCPPR;
SQL>ALTER SYSTEM SET FAL_CLIENT=OCPDR;

Thanks for reading.

I hope you learn something from this article, please write your fillings in the comment box.

Leave a Comment