After deployment of Oracle Database Appliance with OAK 2.3.0 the standard listeners are configured for the public network on bond0. That includes SCAN listeners and one VIP listener per node. This last one seems to listen on both the public network interface and the VIP interface.

However, I would also like something to listen on the management network that I have configured at bond1.

What would be the preferred way of accomplishing this? Can I make the VIP listener also listen to bond1 or must I add a new listener for this?

Can I just add a listener with: srvctl add listener -p TCP:1521 -o /u01/app/

I'm at a loss to see where the ip address or interface goes into the configuration.

Update: Support note 1063571.1 "How to Configure A Second Listener on a Separate Network in 11.2 Grid Infrastructure" covers the addition of a second production listener with associated VIP interfaces (but no second SCAN listener) to a generic 11gR2 RAC.

In this case, as this is meant to be a back door for operators and DBAs, I think it might be OK to have a basic listener directly on the physical interface on each node - eg. one that does not fail over, and only connects to the instances on that specific node.

I suppose there could also be ODA specific considerations that need to be taken into account, although none are too clear to me at this point.

  • Well, the ODA comes with 4 bonded interfaces (8 physical). I'd like to think that it allows for some flexibility in network and listener configuration. 11gR2 RAC in itself certainly allows for multiple listeners on multiple interfaces. I'll add that in this case, I would like a listener for operator and DBA access, away from the production network.
    – Roy
    Oct 18, 2012 at 8:22
  • I have forwarded the question to Oracle Support.
    – Roy
    Oct 19, 2012 at 13:41

1 Answer 1


According to Oracle Support, there should not be any special considerations on Oracle Database Appliance, and thus we can use steps common to Oracle 11gR2 RAC on Linux.

Typically this involves

  • Adding the additional interfaces to /etc/hosts
  • Adding a network resource and virtual ip resources to CRS with srvctl
  • Creating a new listener with netca
  • Adding the new listeners to the LISTENER_NETWORKS initialization parameter

If you want the new listener to live on the default port of 1521, we need to create it on a different port initially, and then manually remove the listener with srvctl and finally re-add the listener on the correct port with srvctl using the -s option. Note that due to a bug in this only works properly on and higher.

Note that the network and vip resources must be added as root, while the rest is done as the grid infrastructure owner. On oda this is "grid".

I wrote at blog post with a more detailed walk-through of how I went about this at http://www.dolicapax.org/?p=116

  • The link you've provided for the walk-through isn't valid any longer (the domain doesn't appear to be online). Is there an updated link that you can provide? I'd like to configure our ODA to have a second SCAN name on a separate subnet and enable client connections from both sources, but I'm being told this isn't possible by somebody who has worked with the ODA before (but it may be the case of not being possible through the wizard, but possible through manual config). Thanks!
    – SqlRyan
    Aug 19, 2015 at 15:25

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.