2 Replies Latest reply: Feb 5, 2013 10:04 AM by CKPT RSS

    FAL_SERVER and FAL_CLIENT in 11.2

    Y.Ramlet
      DB versions: 11.2.0.2, 11.2.0.3
      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 ?
        • 1. Re: FAL_SERVER and FAL_CLIENT in 11.2
          mseberg
          Hello;

          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 :

          http://docs.oracle.com/cd/E11882_01/server.112/e10700/create_ps.htm#i68648

          Best Regards

          mseberg
          • 2. Re: FAL_SERVER and FAL_CLIENT in 11.2
            CKPT
            Y.Ramlet wrote:
            DB versions: 11.2.0.2, 11.2.0.3
            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 ?
            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

            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