Exadata Software - Oracle Exadata Recipes: A Problem-Solution Approach - page 50

TYPE=ora.scan_listener.type
TARGET=ONLINE
STATE=ONLINE on cm01dbm01
NAME=ora.LISTENER_SCAN3.lsnr
TYPE=ora.scan_listener.type
TARGET=ONLINE
STATE=ONLINE on cm01dbm01
[root@cm01dbm01 ~]#
Our database listener, LISTENER , is running on port 1521 and managed by CRS as well. From the compute node
where we're running two SCAN listeners and a database LISTENER , we see the following:
[grid@cm01dbm01 ~]$ srvctl config listener
Name: LISTENER
Network: 1, Owner: grid
Home: <CRS home>
End points: TCP:1521
[grid@cm01dbm01 ~]$ ps -ef|grep tnsl
grid 14924 14310 0 20:59 pts/0 00:00:00 grep tnsl
grid 21887 1 0 15:03 ? 00:00:00 /u01/app/11.2.0.3/grid/bin/tnslsnr
LISTENER_SCAN3 -inherit
grid 21892 1 0 15:03 ? 00:00:00 /u01/app/11.2.0.3/grid/bin/tnslsnr
LISTENER_SCAN2 -inherit
grid 21904 1 0 15:03 ? 00:00:00 /u01/app/11.2.0.3/grid/bin/tnslsnr
LISTENER -inherit
[grid@cm01dbm01 ~]$
In 11gR2, Oracle RAC Virtual IP Addresses, or VIPs, can be listed by running srvctl config nodeapps . In the
following script, we see two VIPs—one on each compute server—on interfaces with the IP addresses 172.16.10.12
and 172.16.10.13 , respectively:
[grid@cm01dbm01 ~]$ srvctl config nodeapps
Network exists: 1/172.16.10.0/255.255.255.0/bondeth0, type static
VIP exists: /cm0101-vip/172.16.10.12/172.16.10.0/255.255.255.0/bondeth0, hosting node cm01dbm01
VIP exists: /cm0102-vip/172.16.10.13/172.16.10.0/255.255.255.0/bondeth0, hosting node cm01dbm02
GSD exists
ONS exists: Local port 6100, remote port 6200, EM port 2016
[grid@cm01dbm01 ~]$
Finally, inside our databases on Exadata, we will have the local_listener and remote_listener initialization
parameters defined with the VIP listener address and SCAN address, respectively: