Query the private interconnect information from the database:
SQL> select * from gv$cluster_interconnects ;
INST_ID NAME IP_ADDRESS IS_ SOURCE
---------- --------------- ---------------- --- -------------------------------
1 eth0 192.168.124.186 NO OS dependent software
Query the private interconnect information using oifcfg:
$ oifcfg getif
eth1 192.168.128.0 global public
eth2 192.168.127.0 global cluster_interconnect
Check the interconnect information from the alert log
And also the alert log will throw the information during start up just after displaying the non-default init parameters:
open_cursors = 300
pga_aggregate_target = 73400320
Cluster communication is configured to use the following interface(s) for this instance
192.168.124.186
You can check the available interfaces using
$ oifcfg iflist
eth0 192.168.124.0
eth1 192.168.128.0
eth2 192.168.127.0
ib1 10.192.2.0
To change the setings follow the below steps:
delete the wrong settings
oifcfg delif -global eth1/192.168.128.0
oifcfg delif -global eth2/192.168.127.0
oifcfg setif -global eth0/192.168.124.0:public
oifcfg setif -global ib1/10.192.2.0:cluster_interconnect
The new settings would take effect after the database bounce.
Note: The crs picks the interconnect information from the /etc/hosts and the database picks from the configuration of oifcfg.
No comments:
Post a Comment