3 Replies Latest reply on Jan 11, 2020 1:56 PM by EdStevens

    Legacy Connectivity: Oracle Net 8 - "bouncing the listener"

    Thomas Hauck

      The concept of "bouncing the listener" existed for tnsnames.ora  during Oracle 8 --> Oracle Net8.

      Does the concept of "bouncing the listener" for Oracle Network Services after

      Oracle 11g still exist?

       

      This is a legacy question and want to know if "bouncing the listener" as a technique has been phased out

      for Oracle Network Services.

      -----

      In the PDF

      Oracle® Database Net Services Administrator's Guide 12c Release 1 (12.1) E17610-12

      on page 41

      1.2.2 About Oracle Net Listener

      Oracle Database server receives the initial connection through Oracle Net Listener.

      Oracle Net Listener, referred to in this document as the listener, brokers a client request, handing off the request to the server. The listener is configured with a protocol

      address, and clients configured with the same protocol address can send connection requests to the listener. When a connection is established, the client and Oracle server

      communicate directly with one another.

       

       

      Question: Does the practice of "bouncing the listener" still exist today?

       

        • 1. Re: Legacy Connectivity: Oracle Net 8 - "bouncing the listener"
          EdStevens

          Thomas Hauck wrote:

           

          The concept of "bouncing the listener" existed for tnsnames.ora during Oracle 8 --> Oracle Net8.

          The "concept" of "bouncing the listener" is exactly the same as the "concept" of "bouncing the database" or "bouncing the server" or "bouncing" any other process.  It is simply stopping and restarting.  So, yes, the "concept" of "bouncing the listener" still exists.  And it has zero, zilch, nada, nyet, null to do with tnsnames.ora.  Where on earth did you get the idea that there was any connection at all?  The listener is a process that runs on the database server.  The tnsnames.ora is nothing more than a file that serves as a  'telephone directory' of databases. As such, it is used only by the client.  Think of it this way:  tnsnemes.ora = telephone directory;  listener process = telephone switchboard.

           

           

           

          1 person found this helpful
          • 2. Re: Legacy Connectivity: Oracle Net 8 - "bouncing the listener"
            Thomas Hauck

            Thank you for your response and feedback.

            -----

            The original question should have been :

            The concept of "bouncing the listener" existed for Oracle Net8, does a similar concept exist for later versions of Oracle Network Services?

            Here is what I found:

            -----

            The tnsnames.ora file is used to store all the details about remote databases.

            Essentially, the tnsnames.ora file pairs a TNS service name with the corresponding host name (or IP address), protocol, and database system ID (SID) name.

             

            Thanks!

            • 3. Re: Legacy Connectivity: Oracle Net 8 - "bouncing the listener"
              EdStevens

              Thomas Hauck wrote:

               

              Thank you for your response and feedback.

              -----

              The original question should have been :

              The concept of "bouncing the listener" existed for Oracle Net8, does a similar concept exist for later versions of Oracle Network Services?

              Here is what I found:

              -----

              The tnsnames.ora file is used to store all the details about remote databases.

              Essentially, the tnsnames.ora file pairs a TNS service name with the corresponding host name (or IP address), protocol, and database system ID (SID) name.

               

              Thanks!

              Please cite your sources.  There is probably more context to the above quote, which is true as far as it goes.  I still don't know why you seemed to think there was some connection between tnsnames.ora and the "Concept" of "bouncing the listener".  And I don't understand why you thought/think that bouncing the listener (which is nothing more that stopping and starting it, just like bouncing any other process) was some sort of "concept" that is tied to a particular version ....

               

              and going one step further, what problem are you trying to solve?