RE: Simple listener parameter question
- From: "Vishal Gupta" <vishal@xxxxxxxxxxxxxxx>
- To: "Dan Norris" <dannorris@xxxxxxxxxxxxx>
- Date: Sun, 7 Dec 2008 04:00:21 -0000
Dan,
You are right, it works fine. I just tried it on 9.2.0.8 and 10.2.0.3 on
linux. But I remember it giving me problems on AIX with 9.2.0.8. Can't
remember the exact scenario and I was hard pressed for time at that
time, so could not dig deeper either.
Regards,
Vishal Gupta
From: Dan Norris [mailto:dannorris@xxxxxxxxxxxxx]
Sent: 06 December 2008 22:08
To: Vishal Gupta
Subject: Re: Simple listener parameter question
alter system set
local_listener='(ADDRESS=(PROTOCOL=TCP)(HOST=my.host.com)(PORT=1521))';
Works for me every time :). Is that what you've tried? What error do you
get?
Dan
On Sat, Dec 6, 2008 at 3:53 PM, Vishal Gupta <vishal@xxxxxxxxxxxxxxx>
wrote:
Last time I tried putting entry directly into local_listener parameter,
oracle did not like it.
Cheers,
Vishal Gupta
On 6 Dec 2008, at 15:09, "Dan Norris" <dannorris@xxxxxxxxxxxxx> wrote:
Personally, I don't like that configuration as it sometimes
confuses people that aren't used to it and they sometimes modify/delete
the TNS entry because they don't know what it is for.
Also, it doesn't give any additional flexibility--anything you
can put in the TNS entry can be jammed on one line and put directly into
this parameter (as long as you don't exceed the length limitations which
I think may be 255 characters).
Dan
On Sat, Dec 6, 2008 at 4:19 AM, Vishal Gupta
<vishal@xxxxxxxxxxxxxxx> wrote:
You can also specify something like. Which gives you more
flexibility in the ability to specify multiple listening address
depending on your listener configuration.
LOCAL_LISTENER=<tnsnamesesalias>
Regards,
Vishal Gupta
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Dan Norris
Sent: 06 December 2008 03:41
To: Mark.Bobak@xxxxxxxxxxxx
Cc: sxmte@xxxxxxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: Re: Simple listener parameter question
I agree on the RAC point--it should be the VIP name/address in a
RAC cluster. I also agree that in most cases for single-instance
database servers you can safely leave it unset. However, I think setting
it to HOST=localhost may only allow connections from the database server
itself since it would cause the listener to listen on 127.0.0.1 and
*not* on other IP addresses (like the "real" IP address of the host). I
can't easily test this right now, but I'm pretty sure it's correct for
current versions. It will also and almost always be affected by whether
or not you specify (IP=FIRST) in the ADDRESS section as well. Have a
look at ML 421305.1 for some really good and relevant information
related to your question.
It is also valid syntax to use (HOST=) and that will also cause
the listener to invoke default behavior and listen on the IP address
that corresponds to the hostname of the server it is running on (or
possibly on 0.0.0.0, which is synonymous with all IP addresses on the
node).
Dan
On Fri, Dec 5, 2008 at 8:40 PM, Bobak, Mark
<Mark.Bobak@xxxxxxxxxxxx> wrote:
Hi Maureen,
One reason I can think of to not use the definition you've
specified, is RAC. In the RAC environment, you'll want to specify a VIP
address for the local listener. Other than that, if you're not on RAC,
leave local_listener unset, and it will default to port 1521 on the
localhost.
Hope that helps,
-Mark
________________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Maureen English
[sxmte@xxxxxxxxxxxxxxxx]
Sent: Saturday, December 06, 2008 1:16 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Simple listener parameter question
Hi,
For those of you who have a LISTENER running on the same machine
as your database(s), do you configure the local_listener
parameter
to have the actual host name, or localhost? Does anyone know of
any reason not to use something like
local_listener='(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1234))'
Other related posts:
