OK, till now, everyone tell me the correct one is the well known one (aka the 1st one I list). But, how about the 3rd one I mentioned, even only set FAL_SERVER in standby site is enough, if consider about role switch, I would add FAL_SERVER=STANDBY in primary site. How about the FAL_CLIENT? any usage? -- Kamus <kamusis@xxxxxxxxx> Visit my blog for more : http://www.dbform.com Join ACOUG: http://www.acoug.org On Wed, Jan 18, 2012 at 2:21 AM, Goulet, Richard <Richard.Goulet@xxxxxxxxxxx> wrote: > You need to set these in view of the database that your setting them on. > Take 2 databases apple1 and apple2: > > on apple1 fal_client would = apple1 and fal_server =apple2 > on apple2 they would be reversed. > > AND BTW: it's best as I've found to use the db_unique_name which does not > have to equal the db_name or the SID, but MUST be unique among the linked > databases.. > > Richard Goulet > Senior Oracle DBA/Na Team Leader > > -----Original Message----- > From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On > Behalf Of Kamus > Sent: Tuesday, January 17, 2012 4:40 AM > To: oracle_l > Subject: FAL_SERVER and FAL_CLIENT > > 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): > > 1. As all we know: > in Primary site: > FAL_SERVER=STANDBY > FAL_CLIENT=PRIMARY > > in Standby site: > 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@xxxxxxxxx> > > Visit my blog for more: http://www.dbform.com Join ACOUG: > http://www.acoug.org Sent with Sparrow (http://www.sparrowmailapp.com/?sig) > > > -- > //www.freelists.org/webpage/oracle-l > > -- //www.freelists.org/webpage/oracle-l