SCAN IP and SCAN Name (Single Client Access Name) 11gR2
——————————————————————————————-
> In 10g and 11gR1 during node additions and deletions, we need to modify the service entries
manually.To overcome this problem in 11gR2 oracle has introduced scan name and scan IP’s.
> Irrespective of the no.of nodes, oracle recommends to have 3 scan IP’s with a single scan name
which will be resolved to any of the scan IP in round robin manner.
Note:subnet mask of public IP,Virtual IP and Scan IP should be same
>During Grid Infrastructure installations, for every scan ip oracle creates one scan vip and scan
listener.
> scan vip and scan listener forms a pair .
> scan ip can be placed either in /etc/hosts or DNS Server.
———————————————————
Service entries in 11gR2
———————————————————
TEST=
(Description=
(Addresslist=(protocol=TCP)(host=cluster-scan.oracle.com)(port=1521)
(loadbalancer=yes)
(service_name=TEST)
——
———-
———-
)
———————————————————-
/etc/hosts
———————————————————-
192.168.128.1 lnx01 lnx01.oracle.com
192.168.128.2 lnx02 lnx02.oracle.com
192.16.128.10 lnx01-priv
192.16.128.11 lnx02-priv
192.16.128.50 lnx01-vip
192.16.128.51 lnx02-vip
192.16.128.100 cluster-scan
192.16.128.101 cluster-scan
192.16.128.102 cluster-scan
————————————————————
DNS Entries
————————————————————
@ IN SOA dns.oracle.com{
—
—
—
}
@ IN NS dns.oracle.com
localhost IN A 127.0.0.1
dns IN A 192.16.128.200
lnx01 IN A 192.16.128.1
lnx02 IN A 192.16.128.2
lnx01-vip IN A 192.16.128.50
lnx02-vip IN A 192.16.128.51
cluster-scan IN A 192.16.128.100
192.16.128.101
192.16.128.102
———————————————————–
In RAC Nodes
———————————————————–
#vi /etc/resolv.conf
nameserver 192.16.128.200
