s advice.
Dave
Rachel wrote:
> Subject: RE: Listeners listening to multiple IPs
> well yeah...
>that's the whole point of USING DNS, so that it will work like that
--- Djordje Jankovic <[EMAIL PROTECTED]> wrote:
> I am not talking whether putting DNS entry works, but am jus
t; > To: Multiple recipients of list ORACLE-L
> > Subject: Re: Listeners listening to multiple IPs
> >
> >
> > it's not so much a feature of the listener as it
> is of DNS as far as I
> > know. One of the reasons it's best not to
> hard-code IP ad
achel
Carmichael To: Multiple recipients of list ORACLE-L
<[EMAIL PROTECTED]>
Subject: RE: Listeners listening to
m
I used to define it on localhost (127.0.0.1) and this worked great with all
ip addresses (only on Solaris).
Did not work on NT!
Regards,
Waleed
-Original Message-
Sent: Tuesday, December 11, 2001 9:40 AM
To: Multiple recipients of list ORACLE-L
Something I learned today, but haven't
cipients of list ORACLE-L
> > Subject: Re: Listeners listening to multiple IPs
> >
> >
> > it's not so much a feature of the listener as it is of DNS as far
> as I
> > know. One of the reasons it's best not to hard-code IP addresses
> into
> >
mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 11, 2001 11:50 AM
> To: Multiple recipients of list ORACLE-L
> Subject: Re: Listeners listening to multiple IPs
>
>
> it's not so much a feature of the listener as it is of DNS as far as I
> know. One of the reaso
1 PM
> To: Multiple recipients of list ORACLE-L
> Subject: Re: Listeners listening to multiple IPs
>
>
> Hi
>
> I did this (don't know wether it's documented or not), but somebody
> recommended to split it up into 2 listeners (1 for each interface) to
> have a bett
Hi
I did this (don't know wether it's documented or not), but somebody
recommended to split it up into 2 listeners (1 for each interface) to
have a better way of controlling the workload (especially with multiple
instances).
Made sense to me.
Djordje Jankovic schrieb:
>
> Something I learned to
it's not so much a feature of the listener as it is of DNS as far as I
know. One of the reasons it's best not to hard-code IP addresses into
the listener.ora is because when you do a failover, or combine machines
as you have, the listener.ora and tnsnames.ora files need to be
updated.
If you use
Something I learned today, but haven't seen it documented anywhere and would
like to see whether anybody has come across it.
We have a Sun server (call it oracle.acme.com). It came to life by
combining two machines (oracle1.acme.com and oracle2.acme.com). So now it
has two IP addresses: hme0: x
10 matches
Mail list logo