1 Reply Latest reply: Sep 25, 2013 4:07 PM by JAGORACLE RSS

    gv$cluster_interconnect does not reflect IP's listed in the /etc/hosts file :11.2.0.3

    1043239

      All during my last maintenance window one my RAC databases could not be started and my investigation pointed to the fact that both nodes had different Cluster_insterconnects values, which is not what is listed in the /etc/hosts file.

       

      SQL> select a.INSTANCE_NAME, b.NAME, b.IP_ADDRESS

      from gv$cluster_interconnects b,

      gv$instance a

      where a.inst_id=b.inst_id;  2    3    4

       

      INSTANCE_NAME    NAME            IP_ADDRESS

      ---------------- --------------- ----------------

      dcxxxx          bond0.404:1     169.254.198.149

      dcxxxx          bond0.404:1     169.254.51.224

       

      After dynamically setting the cluster_interconnects parameter to reflect what is listed in the hosts file i was able to bring up both nodes. I see this problem accross all our RAC environments.

       

      QUESTIONS:

       

      WHAT HAPPENED THAT ORACLE AUTOMATICALLY ASSIGNED RANDOM IP's for cluster interconnects and

      HOW CAN WE PREVENT THIS FROM HAPPENING ?

       

      Any help will be much appreciated.

       

      Colin

        • 1. Re: gv$cluster_interconnect does not reflect IP's listed in the /etc/hosts file :11.2.0.3
          JAGORACLE

          These are called HAIP.These will not be in /etc/hosts.

           

          Grid automatically picks free link local addresses from reserved 169.254.*.* subnet for HAIP. According to RFC-3927, link local subnet 169.254.*.* should not be used for any other purpose. With HAIP, by default, interconnect traffic will be load balanced across all active interconnect interfaces, and corresponding HAIP address will be failed over transparently to other adapters if one fails or becomes non-communicative. .


          Refer :