Services don't register with static listener

Question

HI, no matter what configurations I do the static listener shows no services. Can you help me? Here is my listener.ora:
SID_LIST_LISTENER =
        (SID_LIST =
                (SID_DESC =
                        (GLOBAL_DBNAME=ELLISON9)
                        (ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1)
                        (SID_NAME=ELLISON9)
LISTENER11G =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = ora1)(PORT = 1522))
ADR_BASE_LISTENER = /u01/app/oracle
My tnsnames.ora:
ELLISON9 =
  (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = ora1)(PORT = 1522))
        (CONNECT_DATA =
        (SERVICE_NAME = ELLISON9)
And my parameters in the database are:
service_names=ELLISON9
local_listener=' ';
STATUS of the LISTENER
Alias                     LISTENER11G
Version                   TNSLSNR for Linux: Version 11.2.0.3.0 - Production
Start Date                11-JUN-2013 10:07:09
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File         /u01/app/oracle/product/11.2.0/dbhome_1/log/diag/tnslsnr/ora1/listener11g/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ora1)(PORT=1522)))
The listener supports no services
The command completed successfully
[oracle@ora1 admin]$ sqlplus sys/oracle@ora1:1522/ELLISON9 as sysdba
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor

Answer 1

XerXi wrote:
Isn't the local_listener parameter creating dynamic listener?
I already had a listener named LISTENER from another home and not to confuse both I decided to name it something else. But come to think of it, it wouldn't have been a problem to have 2 listeners with same names but different homes, correct?
No, no, and no.
No. The local_listener parameter doesn't create anything.  It tells the database where to find the listener so that it can register itself with the listener.  And it is only needed if the listener is not using the default port of 1521.
see: [url http://edstevensdba.wordpress.com/2011/07/30/exploring-the-local_listener-parameter/] exploring-the-local_listener-parameter [/url]
No, there is no such this as a 'dynamic listener'.  There is dynamic registration with a listener.  But there is no 'dynamic listener'.  A listener is a listener is a listener.
I don't know if you can have two listeners with the same name running from two different homes or not. I've never been so insane as to try it.  If it *is* possible, it would certainly be the most difficult to maintain multi-listener setup I can imagine.
One more time.  Repeat after me.  "One single listener with the default name  of LISTENER and using the default port of 1521 was designed to support multiple databases of multiple versions running from multiple homes.  Anything else is needless complexity."
Please tell us again what problem you thought you were solving by having multiple listeners ...
Message was edited by: EdStevens