FAL_SERVER and FAL_CLIENT
Date: Tue, 17 Jan 2012 17:40:01 +0800
Message-ID: <A53F7689FADB41C3A17429D7F4FE045C_at_gmail.com>
Hi lists
Maybe this is the question you do not think it should be the question.
for FAL_SERVER and FAL_CLIENT parameter in Data Guard (PRIMARY and STANDBY):
- As all we know: in Primary site: FAL_SERVER=STANDBY FAL_CLIENT=PRIMARY
FAL_SERVER=PRIMARY
FAL_CLIENT=STANDBY 2. As oracle documentation said:
http://docs.oracle.com/cd/E11882_01/server.112/e25513/initparams086.htm#REFRN10056
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.
http://docs.oracle.com/cd/E11882_01/server.112/e25513/initparams085.htm
FAL_CLIENT
specifies the FAL (fetch archive log) client name that is used by the FAL service, configured through the
FAL_SERVER initialization 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).
If I'm not misunderstanding, it should be:
in Primary site:
FAL_SERVER= STANDBY
FAL_CLIENT= STANDBY
in Standby site:
FAL_SERVER=PRIMARY
FAL_CLIENT= PRIMARY
3. As we tested (in Oracle 10.2.0.1), without considering switchover or failover, only set FAL_SERVER=PRIMARY in standby site is enough to fetch archive log from primary site. it means no FAL_SERVER and FAL_CLIENT setting in primary at all, and with no FAL_CLIENT setting in standby site.
So … what do you think?
--
Zhang Leyi (Kamus) <kamusis_at_gmail.com>
Visit my blog for more: http://www.dbform.com
Join ACOUG: http://www.acoug.org
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
--
http://www.freelists.org/webpage/oracle-l
Received on Tue Jan 17 2012 - 03:40:01 CST