Trying to add another DB under SCAN via DBCA "Default listener LISTENER is not Configured in the grid infrastructure home"

Question

Trying to install another DB under RAC using SCAN listener on a new port.  DBCA gives error "Default listener LISTENER is not Configured in the grid infrasturcture home".
Have tried srvctl config listener, srvctl start listener to start the listener.  Still not able to get past the DBCA error.  What am I missing?  Do not want to start LISTENER on port 1521 as SCAN is running on 1521.

Answer 1

No your Database config does use hostname/ip + port or a tns-entry pointing to the local_listener. Neither method does care for the home the listener is running from.
You will however have to take care of the entries in the clusterware, as the listener is a controlled resource. If you manually relocate it, then it will only work until next restart of crs stack.
The simplest way to switch the home is by running first netca from database home and delete the listener and then switch to grid home run netca again and create the listener.
netca will take care of registering it with crs with the correct environment settings. You will have a short period where your rac won't have a listener and therefore won't accept new connections until the new listener is up and running.
Relocating the current listener requires to modify several parameters via crsctl in the cluster registry, but allows doing this node by node without complete outage.
If you want to go that way, then create another listener from grid home and compare the settings of current listener and of the new listener. You will need to update several parameter before you can relocate it.
Run this command to show the current settings and compare it to the listener from grid home:
crsctl stat res ora.LISTENER.lsnr -p
You will need to modify serveral parameters, ACTION_SCRIPT,AGENT_FILENAME,ALIAS_NAME,ORACLE_HOME and the ACL
Modify works like this, for ACL you must use the encasing single apostrophe ' and run it as root:
crsctl modify res ora.LISTENER.lsnr -attr "ACL='owner:oracle:rwx,pgrp:oinstall:rwx,other::r--'"
I would recommend Version 1 if short outage is acceptable. For both variants verify that you can resolve all tnsnames entries in both homes.
Regards
Thomas