FAL_SERVER and FAL_CLIENT

Max4rDBA
Max4rDBA used Ask the Experts™
on
Hello Guys,

I have one doubt, i am currently doing a dataguard configuration.

In this one Let say i have primary1 and standyby1 database.

Is the following configuration is correct(Current Setup) ..

In Primary :
FAL_SERVER = PRIMARY1
FAL_CLIENT = STDBY1

In Standby :
FAL_SERVER = STDBY1
FAL_CLIENT = PRIMARY1.

When Failover is done ...

In Primary :
FAL_SERVER = STDBY1
FAL_CLIENT = PRIMARY1.

In Standby :
FAL_SERVER = PRIMARY1
FAL_CLIENT = STDBY1

or where ever i read in the net its like reverse of the above one mentioned settings.

I have already searched in the google, but i am confused. Any help would be appreciated.

Thanks

Rahul




Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Nope, it is the reverse.

The way to remember it is that what is on the primary doesn't even matter really, and the standby needs to be told via FAL_SERVER what is the primary?

Commented:
See, in general there is no need to configure FAL_SERVER and FAL_CLIENT in initialization parameter file of primary database.

You need to specify this parameter in standby database only, like,
FAL_SERVER=Primary_server_service_name
FAL_CLIENT=Standby_server_service_name

But, Sometime you see some documents on net which show configuratino of this parameter in primary init file also. That is use to ensure smooth running when role reversal happen.

So, when role reversal happen your primary database become standby database, and that time you need to configure FAL_SERVER and FAL_CLIENT in init paramete file on primary database.
FAL_SERVER=standby_server_which_Become_primary_now_service_name
 FAL_CLIENT=Primary_server_which_is_now_standby_service_name
 
 
Hi,

Hope the below will clear you doubt...


FAL  -  Fetch Archive logs



The FAL_SERVER and FAL_CLIENT are standby database parameters i.e it will be in effect if your
database is a standby database.


FAL_SERVER --> From where to fetch the archive logs.
FAL_CLINET --> to where the fetched archived logs from the server to be applied.


As you know the standby database are recoverd by appling the archive logs that
been transported from the primary database to the standby database.

so in you standby database we will mention as below


FAL_SERVER = your_primary_database_netserivce_name -- because your primary database is the server for your standby database




So in primary database we will mention as below

FAL_SERVER = your_standby_database_servcie_name --

(Since if you do a switch over your primary datbase will become standby database and your standby database
will become the primary database, now these standby parameter (FAL_sERVER and fal_client) will get activated in your
old primary database (which is now became the standby database)
all the logs (redo, archive) will be generated in your new primary database (which is the old standby),
now your current standby database (i.e. your old primary databse)
will start fetching the archvie log from the current priarmy database (which is the old standby)
which you have mentioned in FAL_SERVER , and the fetched logs will be applied in your priarmy database (currently
running as standby database)


So while configuring the standby database

in primary database you should configure the parameter as below

FAL_SERVER = your_standby_databae_netservice_name
FAL_CLIENT = you_priarmy_database_netservice_name


and in standby database you should configure the parameters as below

FAL_SERVER = your_primary_database_netservice_name
FAL_CLIENT = your_standby_database_netservice_name


Thanks..
S. Manzoor








Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial