{"id":116,"date":"2012-10-24T00:01:32","date_gmt":"2012-10-23T22:01:32","guid":{"rendered":"http:\/\/www.dolicapax.org\/?p=116"},"modified":"2012-10-24T12:22:51","modified_gmt":"2012-10-24T10:22:51","slug":"adding-an-additional-listener-to-oda","status":"publish","type":"post","link":"https:\/\/www.dolicapax.org\/?p=116","title":{"rendered":"Adding an additional listener to ODA"},"content":{"rendered":"

After deploying an Oracle Database Appliance, a standard set of production listeners are configured on bond0.<\/em> This includes one listener on each of the virtual ip interfaces, and two SCAN listeners.<\/p>\n

In my environment, I would very much like to have additional listeners on bond1. <\/em>I use this as a management network, and find it convenient to let DBAs and operators run their tools over this network.<\/p>\n

According to Oracle Support, there should not be any special considerations on ODA, and thus we can follow support note ID\u00a01063571.1 just like we would with any other 11gR2 RAC\u00a0infrastructure.<\/p>\n

In my humble opinion, this particular support note isn’t too clear even if you have access to My Oracle Support, so I’ll describe the steps I used for my setup:<\/p>\n

Production network on bond0 is 10.20.30.0\/24
\nManagement network on bond1 is 192.168.0.0\/24<\/p>\n

First out we need host file entries on both nodes for the new VIP interfaces:<\/p>\n

\/etc\/hosts:<\/p>\n

# VIP HOSTNAMES
\n10.20.30.42 oda1-vip.dolicapax.org oda1-vip
\n10.20.30.43 oda2-vip.dolicapax.org oda2-vip<\/p>\n

192.168.0.23 oda1m-vip.dolicapax.org oda1m-vip<\/strong>
\n192.168.0.24 oda2m-vip.dolicapax.org oda2m-vip<\/strong><\/p><\/blockquote>\n

Next we add the virtual ip interfaces to CRS. The network resource (specified with the -k 2 option) should be create implicitly:<\/p>\n

 <\/p>\n

su – root
\ncd\u00a0\/u01\/app\/11.2.0.3\/grid\/bin\/
\n.\/srvctl add vip -n oda1 -k 2 -A 192.168.0.23\/255.255.255.0\/bond1
\n.\/srvctl add vip -n oda2 -k 2 -A 192.168.0.24\/255.255.255.0\/bond1<\/p><\/blockquote>\n

We can verify that the network resource and the virtual ip interfaces have been created with crsctl:<\/em><\/p>\n

[root@oda1 bin]# .\/crsctl stat res -t |grep -E ‘net|vip’
\nora.net1.network
\nora.net2.network<\/strong>
\nora.oda1.vip
\nora.oda1m-vip.vip<\/strong>
\nora.oda2.vip
\nora.oda2m-vip.vip<\/strong>
\nora.scan1.vip
\nora.scan2.vip<\/p><\/blockquote>\n

The final step is to create the actual listener. Oracle reccomends that you do this with the \u00a0network configuration assistant netca.\u00a0<\/em>The command must be run from the grid user.<\/p>\n

roy@kayna:~$ ssh oda1 -l grid -X
\ngrid@oda1’s password:
\nLast login: Tue Oct 23 22:15:41 2012 from 192.168.0.46
\n\/usr\/bin\/xauth: creating new authority file \/home\/grid\/.Xauthority
\n[grid@oda1 ~]$ netca<\/p><\/blockquote>\n

Just select Listener confguration<\/em> and then Add<\/em> and walk through the wizard, selecting the correct network resource (subnet) along the way. Note that netca<\/em>\u00a0sees the original listener on\u00a0\u00a0default port of 1521, and will not allow another on the same port. I went with a name of LISTENER_M and a port of 1522 for my configuration.<\/p>\n

This will take care of both listener.ora and OCR configuration.<\/p>\n

However, I really do want the new listener to be listening the default port of 1521. netca\u00a0<\/em>complains that another listener is already configured on this port, even though it’s not on the same interface. The workaround is to manually remove and recreate the listener with srvctl using the -s option.<\/p>\n

su – grid
\nsrvctl stop listener -l LISTENER_M
\nsrvctl remove listener LISTENER_M
\nsrvctl add listener -l LISTENER_M -s -p 1521 -k 2
\nsrvctl start listener -l LISTENER_M<\/p><\/blockquote>\n

We’re all set, and can now see the new listener (along with the default listeners) on the correct interface and port using netstat<\/em>.<\/p>\n

[grid@oda1 ~]$ netstat -ln | grep 1521
\ntcp 0 0 192.168.0.23:1521 0.0.0.0:* LISTEN<\/strong>
\ntcp 0 0 10.20.30.32:1521 0.0.0.0:* LISTEN
\ntcp 0 0 10.20.30.30:1521 0.0.0.0:* LISTEN
\ntcp 0 0 10.20.30.34:1521 0.0.0.0:* LISTEN
\n[grid@oma1 ~]$ ssh oma2
\n[grid@oma2 ~]$ netstat -ln | grep 1521
\ntcp 0 0 192.168.0.24:1521 0.0.0.0:* LISTEN\u00a0<\/strong>
\ntcp 0 0 10.20.30.33:1521 0.0.0.0:* LISTEN
\ntcp 0 0 10.20.30.31:1521 0.0.0.0:* LISTEN
\ntcp 0 0 10.20.30.35:1521 0.0.0.0:* LISTEN<\/p><\/blockquote>\n

or with lsnrctl<\/p>\n

[grid@oda2 ~]$ lsnrctl status LISTENER_M<\/p>\n

LSNRCTL for Linux: Version 11.2.0.3.0 – Production on 23-OCT-2012 22:47:00<\/p>\n

Copyright (c) 1991, 2011, Oracle. All rights reserved.<\/p>\n

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_M)))
\nSTATUS of the LISTENER
\n————————
\nAlias LISTENER_M
\nVersion TNSLSNR for Linux: Version 11.2.0.3.0 – Production
\nStart Date 23-OCT-2012 22:36:49
\nUptime 0 days 0 hr. 10 min. 13 sec
\nTrace Level off
\nSecurity ON: Local OS Authentication
\nSNMP OFF
\nListener Parameter File \/u01\/app\/11.2.0.3\/grid\/network\/admin\/listener.ora
\nListener Log File \/u01\/app\/11.2.0.3\/grid\/log\/diag\/tnslsnr\/oda2\/listener_m\/alert\/log.xml
\nListening Endpoints Summary…
\n(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER_M)))
\n(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.0.24)(PORT=1521)))
\nThe listener supports no services
\nThe command completed successfully<\/p><\/blockquote>\n

As you can see, the listener is up but supporting no services. Unless we want this to be a static listener, we need to tell the database to make it’s presence known.<\/p>\n

We accomplish this by using the new LISTENER_NETWORKS parameter.<\/p>\n

SQL> alter system set listener_networks = ‘((NAME=MGMT_NET)(LOCAL_LISTENER=oda1m-vip:1521)(REMOTE_LISTENER=oda2m-vip:1521))’ SID=’testdb1′ SCOPE=both;<\/p>\n

System altered.<\/p>\n

SQL> alter system set listener_networks = ‘((NAME=MGMT_NET)(LOCAL_LISTENER=oda2m-vip:1521)(REMOTE_LISTENER=oda1m-vip:1521))’ SID=’testdb2′ scope=both;<\/p>\n

System altered.<\/p><\/blockquote>\n

A new look at the listener status will show that the instances are now properly registered:<\/p>\n

Services Summary…
\nService “TESTDB” has 2 instance(s).
\nInstance “TESTSB1”, status READY, has 1 handler(s) for this service…
\nInstance “TESTDB2”, status READY, has 1 handler(s) for this service…
\nThe command completed successfully<\/p><\/blockquote>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

After deploying an Oracle Database Appliance, a standard set of production listeners are configured on bond0. This includes one listener on each of the virtual ip interfaces, and two SCAN listeners. In my environment, I would very much like to … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,20,4],"tags":[26,35,25,18,24],"class_list":["post-116","post","type-post","status-publish","format-standard","hentry","category-oda-oracle","category-oracle","category-tech","tag-11gr2","tag-listener","tag-network","tag-oda","tag-oracle-2"],"_links":{"self":[{"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=\/wp\/v2\/posts\/116","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=116"}],"version-history":[{"count":7,"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=\/wp\/v2\/posts\/116\/revisions"}],"predecessor-version":[{"id":123,"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=\/wp\/v2\/posts\/116\/revisions\/123"}],"wp:attachment":[{"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=116"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=116"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=116"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}