| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Questions re LOCAL_LISTENER & REMOTE_LISTENER
Greetings, thanks to all, I see where I was going wrong. Now all I have
to do is get the syntax of my tnsnames.ora correct.
Thanks.
Bill Wagman
Univ. of California at Davis
IET Campus Data Center
wjwagman_at_ucdavis.edu
(530) 754-6208
-----Original Message-----
From: Herring Dave - dherri [mailto:Dave.Herring_at_acxiom.com]
Sent: Monday, November 19, 2007 1:29 PM
To: William Wagman; Andreas Piesk
Cc: oracle-l_at_freelists.org
Subject: RE: Questions re LOCAL_LISTENER & REMOTE_LISTENER
Correct me if I'm wrong, but I believe this is where you include "SID = ..." on the ALTER SYSTEM SET command.
If you're following metalink doc 226880.1, local_listener would be set using something like:
# On node1, instance1
ALTER SYSTEM SET local_listener = LISTENER_NODE1 SID = instance1;
# On node2, instance2
ALTER SYSTEM SET local_listener = LISTENER_NODE2 SID = instance2;
That way you'll end up with something like: instance1.local_listener = LISTENER_NODE1 instance2.local_listener = LISTENER_NODE2
I believe the reply below had the intent of setting local_listener = LOCAL_LISTENER, then the service LOCAL_LISTENER is set differently in each node's tnsnames.ora file.
Dave
David C. Herring, DBA | A c x i o m Delivery Center Organization
630-944-4762 office | 630-430-5988 wireless | 630-944-4989 fax
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]
> On Behalf Of William Wagman
> Sent: Monday, November 19, 2007 2:26 PM
> To: Andreas Piesk
> Cc: oracle-l_at_freelists.org
> Subject: RE: Questions re LOCAL_LISTENER & REMOTE_LISTENER
>
> Andreas,
>
> Thanks for the reply. But this is where I think I may be missing
> something. As I see it the LOCAL_LISTENER parameter is an init
parameter
> and with a shared SPFILE it is the same on each node. How do I
configure
> it to point to the local node? I am probably missing something very
> basic here so bear with me.
>
> Thanks.
>
>
> Bill Wagman
> Univ. of California at Davis
> IET Campus Data Center
> wjwagman_at_ucdavis.edu
> (530) 754-6208
> -----Original Message-----
> From: Andreas Piesk [mailto:a.piesk_at_gmx.net]
> Sent: Saturday, November 17, 2007 5:21 AM
> To: William Wagman
> Cc: oracle-l_at_freelists.org
> Subject: Re: Questions re LOCAL_LISTENER & REMOTE_LISTENER
>
> William Wagman schrieb:
> >
> > And the mirror image on node 2. This is puzzling to me as the
> > tnsnames.ora listed in example 9.1 of the Real Application Clusters
> > Installation guide looks like the one I currently have. I think my
> lack
> > of understanding has to do with how the local and remote listener
> > parameters function so if someone could help me in my understanding
I
> > would be most grateful.
>
> you're right, LOCAL_LISTENER on each node should point to the listener
> on that node. REMOTE_LISTENER should point to all listeners on all
nodes
> if you want server side load balancing, otherwise don't set
> REMOTE_LISTENER.
>
> so to make your configuration right, you should setup it like this:
>
> node1:
>
> LOCAL_LISTENER_NODE1 =
> (ADDRESS_LIST =
> (ADDRESS =
> (PROTOCOL = TCP)
> (HOST = node1-vip)
> (PORT = 1521)
> )
> )
> REMOTE_LISTENERS =
> (ADDRESS_LIST =
> (ADDRESS =
> (PROTOCOL = TCP)
> (HOST = node1-vip)
> (PORT = 1521)
> )
> (ADDRESS =
> (PROTOCOL = TCP)
> (HOST = node2-vip)
> (PORT = 1521)
> )
> )
>
> LOCAL_LISTENER=LOCAL_LISTENER_NODE1
> REMOTE_LISTENER=REMOTE_LISTENERS
>
>
> node2:
>
> LOCAL_LISTENER_NODE2 =
> (ADDRESS_LIST =
> (ADDRESS =
> (PROTOCOL = TCP)
> (HOST = node2-vip)
> (PORT = 1521)
> )
> )
> REMOTE_LISTENERS =
> (ADDRESS_LIST =
> (ADDRESS =
> (PROTOCOL = TCP)
> (HOST = node1-vip)
> (PORT = 1521)
> )
> (ADDRESS =
> (PROTOCOL = TCP)
> (HOST = node2-vip)
> (PORT = 1521)
> )
> )
>
> LOCAL_LISTENER=LOCAL_LISTENER_NODE2
> REMOTE_LISTENER=REMOTE_LISTENERS
>
>
> on a 2-node cluster your REMOTE_LISTENER can point to a single
listener
> but i find it easier to keep REMOTE_LISTENER identical on all nodes.
>
> the purpose of REMOTE_LISTENER is to connect all instances with all
> listeners so the instances can propagate their load balance advisories
> to all listeners. if you connect to a listener, this listener uses the
> advisories to decide who should service your connect. if the listener
> decides its local instance(s) are least loaded and should service your
> connect it passes your connect to the local instance. if the node you
> connected to is overloaded, the listener can use TNS redirect to
> redirect your connect a less loaded instance.
>
>
> regards,
> -ap
> --
> http://www.freelists.org/webpage/oracle-l
>
If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.
If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system.
Thank You.
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Nov 19 2007 - 17:06:51 CST
 |
 |