1 Reply Latest reply on Jul 1, 2020 10:33 AM by Maaz Khan

    scan - EBS r12.2.5

    3510875

      Hi Experts,

       

      Our db version 12.1.0.2 2 node rac

      2 node application R12.2.5 shared

       

      Currently our tnsnames.ora have 3 scan vip's in our application nodes instead of scan name.

       

      [oraprod@proddb1 ~]$ srvctl status scan

      SCAN VIP scan1 is enabled

      SCAN VIP scan1 is running on node proddb1

      SCAN VIP scan2 is enabled

      SCAN VIP scan2 is running on node proddb2

      SCAN VIP scan3 is enabled

      SCAN VIP scan3 is running on node proddb2

      [oraprod@proddb1 ~]$

       

      our scan name : SCAN name: erpprod-scan.xyz.com

       

      TNS entries in application node

       

      PRODDB_BALANCE=

              (DESCRIPTION=

                  (ADDRESS_LIST=

                      (LOAD_BALANCE=YES)

                      (FAILOVER=YES)

                      (ADDRESS=(PROTOCOL=tcp)(HOST=172.19.120.80)(PORT=1521))

                      (ADDRESS=(PROTOCOL=tcp)(HOST=172.19.120.79)(PORT=1521))

                      (ADDRESS=(PROTOCOL=tcp)(HOST=172.19.120.81)(PORT=1521))

                  )

                  (CONNECT_DATA=

                      (SERVICE_NAME=PRODDB)

                  )

              )

       

      All these are scan VIP's.will scan canot support scan name instead of scan VIPS?

        • 1. Re: scan - EBS r12.2.5
          Maaz Khan

          Hello,

           

          There are few things you need to consider and check in your environment -

          1. sqlnet.ora configuration.

          2. value of remote_listener

          3. Changes in tnsnames.ora file after executing autoconfig.

          4. autoconfig version.

           

          Below is reference note from MOS for you-

          SCAN Registration Issue: Services Fail to Register to SCAN Listeners (Doc ID 1448717.1

           

          I have documented few things under -

          https://maazdba.blogspot.com/2019/03/implications-of-autoconfig-on-rac-setup.html

           

           

          Summarising this, you can use scan entry provided your sqlnet.ora has configuration like below, -

          NAMES.DIRECTORY_PATH=(EZCONNECT, TNSNAMES))

           

          This implies  EZCONNECT having higher preference than TNSNAMES and value of REMOTE_LISTENER will be resolved by EZCONNECT method first.

           

          Considering other way like below -

          NAMES.DIRECTORY_PATH=(TNSNAMES, EZCONNECT))

          This will resulting in name getting resolved by entry found in tnsnames.ora.

           

          Hope this helps.

           

           

          Regards,

          Maaz

           

           

           

          1 person found this helpful