 | | | -none- | -none- 2007-08-14 - By Niall Litchfield
Back
On 8/14/07, Dunbar, Norman <norman.dunbar@(protected)> wrote:
>
>
> Morning
>
> >> I knew that is problem, but based on ORACLE say you
> >> can Only turn on one listener which is highest version
> >> of ORACLE.
>
> Hopefully, you will have got your tnsnames problems sorted out by now.
> However, the advice to only use one listener and to use the highest
> version of Oracle software is pretty sound - if you intend to run all
> your databases (on that server) using the same listener.
I have a clustered server system to look after and each 'package' can
> failover between cluster nodes in the event of a problem. I have one
> listener per database and that one listener is running with the same
> version of Oracle as the database itself.
>
> Obviously, I cannot have 'hundreds' of listeners all called LISTENER, so
> they each have individual names like Horace and Stella or Derek and
> Rachel.
:)
Only kidding :o) The names are related to the package name - that makes
> it easy to identify them and also to auto start them in the package
> start-up scripts.
Unless - like us on our dev boxes - you have many different Oracle software
owners I'm not sure that net services aren't a better solution for this sort
of thing than multiple listeners. (I'm assuming the environment agency is at
least at 8i).
--
Niall Litchfield
Oracle DBA
http://www.orawin.info
<div><span class="gmail_quote">On 8/14/07, <b class="gmail_sendername">Dunbar,
Norman</b> <<a href="mailto:norman.dunbar@(protected)">norman
.dunbar@(protected)</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0
.8ex; BORDER-LEFT: #ccc 1px solid"><br>Morning<br><br>>> I knew that is
problem, but based on ORACLE say you<br>>> can Only turn on one listener
which is highest version
<br>>> of ORACLE.<br><br>Hopefully, you will have got your tnsnames
problems sorted out by now.<br>However, the advice to only use one listener and
to use the highest<br>version of Oracle software is pretty sound - if you
intend to run all
<br>your databases (on that server) using the same listener.</blockquote>
<div> </div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0
.8ex; BORDER-LEFT: #ccc 1px solid">I have a clustered server system to look
after and each 'package' can<br>failover between cluster nodes in the
event of a problem. I have one
<br>listener per database and that one listener is running with the same<br
>version of Oracle as the database itself.<br><br>Obviously, I cannot have '
;hundreds' of listeners all called LISTENER, so<br>they each have individual
names like Horace and Stella or Derek and
<br>Rachel.</blockquote>
<div> </div>
<div>:) </div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0
.8ex; BORDER-LEFT: #ccc 1px solid">Only kidding :o) The names are
related to the package name - that makes<br>it easy to identify them and also
to auto start them in the package
<br>start-up scripts.</blockquote>
<div> </div></div>
<div>Unless - like us on our dev boxes - you have many different Oracle
software owners I'm not sure that net services aren't a better solution
for this sort of thing than multiple listeners. (I'm assuming the
environment agency is at least at 8i).
</div>
<div> </div>
<div><br>-- <br>Niall Litchfield<br>Oracle DBA<br><a href="http://www.orawin
.info">http://www.orawin.info</a> </div>
|
|
|