Database Reference
In-Depth Information
However, ASM instance mapping cannot be changed that easily, since the ASM instance name is dynamically
derived from the node number. Updating the node number would require Clusterware reconfiguration, as the node
number to node name mapping is stored in the voting disk.
$ crsctl stat res ora.asm -p |grep INST_NAME
..
GEN_USR_ORA_INST_NAME@SERVERNAME(RAC1)=+ASM1
GEN_USR_ORA_INST_NAME@SERVERNAME(RAC2)=+ASM2
USR_ORA_INST_NAME=+ASM%CRS_CSS_NODENUMBER%
In a cluster with a large number of nodes, it is typical to keep the node name with an incrementing suffix, such
as RAC1, RAC2, RAC3, etc. It is also a matter of convenience to keep suffixes of both database and ASM instances
matching with node name suffixes; for example, ORCL1 and ASM1 instance in RAC1 node, ORCL2 and ASM2 instance
in RAC2 node, etc. As the node number is assigned at the time of cluster configuration, execute root.sh in the order
desired; for example, execute root.sh in RAC1 node, wait for completion, execute root.sh in RAC2 node, wait for
completion, etc. This execution order will maintain correct suffix mapping.
Managing VIPs, Listeners
To manage VIPs and listeners, use of the srvctl command is recommended. Configuration of VIP can be queried using
the
config vip
parameter.
$ srvctl config vip -n RAC1
VIP exists.:RAC1
VIP exists.: /RAC1_vip/1.2.1.101/255.255.255.0/eth1
$ srvctl config vip -n RAC2
VIP exists.:RAC2
VIP exists.: /RAC2_vip/1.2.1.102/255.255.255.0/eth1
VIPs can be started and stopped using the srvctl command, but Clusterware daemons usually monitor these
resources, and so these commands are seldom used.
$ srvctl stop vip -n RAC2
$ srvctl start vip -n RAC2
Similarly, listeners can be managed using the srvctl command. For example, configuration of a listener can be
queried using the following config command.
$ srvctl config listener -l LISTENER
Name: LISTENER
Network: 1, Owner: oracle
Home: <CRS home>
End points: TCP:1521
Listeners can be stopped and started using the srvctl command with the following syntax. Executing the lsnrctl
command is not a recommended practice.
$ srvctl stop listener -l LISTENER
$ srvctl start listener -l LISTENER
