This content has been marked as final. Show 2 replies
Hello;1 person found this helpful
I would always set FAL_SERVER. FAL_CLIENT is not required in 11.2, but can be set depending upon your exact setup.
FAL_CLIENT is not even needed in most Oracle 11 Data Guard setups :
http://docs.oracle.com/cd/E11882_01/server.112/e25608/whatsnew.htm ( The FAL_CLIENT database initialization parameter is no longer required. )
See Chapter 3 of oracle document E25608-04 for exact details :
1 person found this helpful
Y.Ramlet wrote:FAL_SERVER & FAL_CLIENT used for the gap resolution, FAL_CLIENT is the system receiving archivelogs. So better to configure where this can work efficiently to resolve the GAP
DB versions: 220.127.116.11, 18.104.22.168
Platform : RHEL 6, Solaris 10
2-Node RAC, Maximum Availability Mode
Starting from 11.2 , FAL_SERVER and FAL_CLIENT parameters do not have to be set at the standby DB side. Right ?
Read parameter in detail here
FAL_CLIENT --> http://docs.oracle.com/cd/E11882_01/server.112/e17110/initparams086.htm
FAL_SERVER --> http://docs.oracle.com/cd/E14072_01/server.112/e10820/initparams081.htm
Apologize, for the latest patchset of 11.2 you no need to mention FAL_CLIENT. Mseberg mentioned perfect link. Thank you.
Edited by: CKPT on Feb 5, 2013 9:33 PM