Database Reference
In-Depth Information
STOP_DEPENDENCIES=hard(ora.net1.network)
...
USR_ORA_VIP=10.11.45.99
VERSION=12.1.0.0.0
As the subnet value is coded in the ora.net1.network resource, SCAN VIP also should be in the same subnet as
other VIP resources. All VIPs and SCAN VIPs of a network should be configured in the same subnet. You can query the
SCAN details using the following srvctl command. By specifying an ordinal number with -i flag, command output is
filtered to just the SCAN1 resource.
$ srvctl config scan -i 1
SCAN name: rac1-scan, Network: 1/10.11.45.0/255.255.254.0/eth1:eth2
SCAN VIP name: scan1, IP: /rac-scan.local.net/10.11.45.99
Similarly, SCAN listener is configured as a resource specifying port number and protocol. SCAN listener is a
dependent resource of ora.scan1.vip.
$ crsctl stat res ora.LISTENER_SCAN1.lsnr -p |more
NAME=ora.LISTENER_SCAN1.lsnr
TYPE=ora.scan_listener.type
...
PORT=25000
...
START_DEPENDENCIES=hard(ora.scan1.vip) dispersion:active(type:ora.scan_listener.type) pullup(ora.
scan1.vip)
...
STOP_DEPENDENCIES=hard(intermediate:ora.scan1.vip)
Up to version 11gR2, SCAN IP addresses were required to be in the first network only. Version 12c allows you to
create SCAN listeners and SCAN IP addresses in the second network also.
In summary, the resource ora.net1.network captures the subnet and netmask details; resource ora.scan1.vip
captures the VIP address and is dependent on ora.net1.network resource; and ora.LISTENER_SCAN1.lsnr captures
the protocol and port number details, and is dependent on ora.scan1.vip type. Any state change in a resource will
trigger dependent resources to be restarted or stopped.
Private Network
Private network configuration is also stored in OCR, and OCR can be stored in ASM from Database version 11g
onward. However, during Clusterware startup, the CSSD daemon is started earlier than the ASM instance. So, a few
critical details are required for HAS startup and are captured in an XML file and Oracle Local Registry (OLR).
The following lines show cluster_interconnect details in the profile.xml file.
$ cd $ORACLE_HOME/gpnp/profiles/peer/
$ grep 172 profile.xml
...
<gpnp:Network id="net3" IP="172.18.1.0" Adapter="eth3" Use="cluster_interconnect"/>
<gpnp:Network id="net4" IP="172.18.2.0" Adapter="eth4" Use="cluster_interconnect"/>
...
