Re: Two instances, two listeners and /etc/services

Johnny Chan <j4ychan_at_PROBLEM_WITH_INEWS_GATEWAY_FILE> wrote:
>However, I would like to point out that you don't need a separate listener
>for each instance on the same node: In all but a few exceptions, a single
>listener is able to handle connections into multiple instances in the same
>node. You merely have to configure the /etc/listener.ora file properly so

I've tried to configure my listener.ora to handle for multiple instances but it seemed that sometimes the listener connects the user to the wrong instance. The log file shows that the listener has connected the user to the correct sid.
  What I had for my listener.ora is like this:

(ADDRESS_LIST =

      ( 
       key for first instance
      )
      ( 
       key for second instance
      )
     (
	community ,host,port for the listener used
     )

And under my tnsnames.ora file, I have

first instance = (

        description and connect data info
       ) 
second instance = (
        description and connect data info
       ) 

Thanks for any advice rendered.

>that the listener listens for connection requestions to multiple instances
>on one port. A single listerner-per-node configuration is actually a lot
>more easier to manage from the client program perspective since the
>client tnsnames.ora will all have the same port number for all remote
>databases.

-- 
Choon Leong