9 Replies Latest reply: Apr 26, 2013 8:59 AM by EdStevens RSS

    Listener Error

    yxes2013
      Hi All,

      11.2.0.1

      What happened to my listener? I just change it to an IP from localhost so that the remote client can connect.

      But now it got no support services error :( Helpppp
      [oracle@orabckup ~]$ lsnrctl status
      
      LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 26-APR-2013 12:09:16
      
      Copyright (c) 1991, 2009, Oracle.  All rights reserved.
      
      Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.0.0.21)(PORT=1521)))
      STATUS of the LISTENER
      ------------------------
      Alias                     LISTENER
      Version                   TNSLSNR for Linux: Version 11.2.0.1.0 - Production
      Start Date                26-APR-2013 12:06:32
      Uptime                    0 days 0 hr. 2 min. 44 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/diag/tnslsnr/orabckup/listener/alert/log.xml
      Listening Endpoints Summary...
        (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.0.0.21)(PORT=1521)))
      The listener supports no services
      The command completed successfully
        • 1. Re: Listener Error
          sb92075
          listener does not require listener.ora file.

          your listener.ora is mis-configured
          • 2. Re: Listener Error
            cherrydba
            try
            lsnrctl reload
            lsnrctl status
            • 3. Re: Listener Error
              Girish Sharma
              Check below and similar threads got from Google when I said "The listener supports no services" to Google.

              Please always do some effort to solve the problem, so that "Problems" knows next door next time.... :)

              The listener support no services

              Regards
              Girish Sharma
              • 4. Re: Listener Error
                sb92075
                %bala% wrote:
                try
                lsnrctl reload
                lsnrctl status
                ridiculous waste of effort & keystroke,
                since root cause is OS/networking mis-configuration.
                • 5. Re: Listener Error
                  Kh$n
                  Best practice is to use hostname in your configuration files instead of ip address.
                  please provide
                  1) what is your current host ip address???
                  2) post content of /etc/hosts.

                  Edited by: Kh$n on Apr 25, 2013 10:04 PM
                  • 6. Re: Listener Error
                    yxes2013
                    ok issue solved by adding SID_LIST_LISTENER. :)
                    • 7. Re: Listener Error
                      EdStevens
                      yxes2013 wrote:
                      ok issue solved by adding SID_LIST_LISTENER. :)
                      Actually, it most likely would have resolved itself if you had just waited a couple of minutes. When relying on dynamic registration, of course when the listener first comes up it will not know of any services. It will take a minute or two for the databases to register themselves with it.
                      • 8. Re: Listener Error
                        sb92075
                        EdStevens wrote:
                        yxes2013 wrote:
                        ok issue solved by adding SID_LIST_LISTENER. :)
                        Actually, it most likely would have resolved itself if you had just waited a couple of minutes.
                        Hmmm, Errrr. based upon first post in this thread (as shown below) above is not correct.
                        Uptime 0 days 0 hr. 2 min. 44 sec
                        • 9. Re: Listener Error
                          EdStevens
                          sb92075 wrote:
                          EdStevens wrote:
                          yxes2013 wrote:
                          ok issue solved by adding SID_LIST_LISTENER. :)
                          Actually, it most likely would have resolved itself if you had just waited a couple of minutes.
                          Hmmm, Errrr. based upon first post in this thread (as shown below) above is not correct.
                          Uptime 0 days 0 hr. 2 min. 44 sec
                          Good catch. So it would appear he introduced a mismatch between the listener and the ability of the instances to register themselves, then put a band-aid on it by adding SID_LIST to the listener.ora.