Re: 11.2.0.2: Why is the local listener listening on public ip?
- From: Jozsef Horvath <horvathjozsef@xxxxxxxxx>
- To: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- Date: Mon, 8 Nov 2010 16:53:38 +0000
Hi Niall,
I believe the client here means the connection descriptor and not the
OCI/JDBC/etc environment. So, if you have, say, tens or hundreds clients
where it is not possible to change the connection descriptor everywhere then
the clients pointed to the static IPs will still be able to connect to your
RAC environment. I find this to be the only reasonable explanation. Makes
sense?
-- Jozsef
On 8 November 2010 16:27, Niall Litchfield <niall.litchfield@xxxxxxxxx>wrote:
> Am I alone in not understanding the explanation (its been a loong weekend).
> surely the vip is only an IP address. Why can't previous clients connect to
> a listener on a VIP?
>
> On Mon, Nov 8, 2010 at 4:09 PM, Jozsef Horvath <horvathjozsef@xxxxxxxxx>wrote:
>
>> Hi,
>>
>> Interesting enought that I have just had a conversation with colleagues
>> about this a couple of days ago.
>> Briefly: (extracted from Oracle Metalink note 220970.1)
>> "Why does netca always creates the listener which listens to public ip and
>> not VIP only? This is for backward compatibility with existing clients:
>> consider pre-10g to 10g server upgrade. If we made upgraded listener to only
>> listen on VIP, then clients that didn't upgrade will not be able to reach
>> this listener anymore. "
>>
>> Hope this helps.
>> --Jozsef
>>
>>
>> On 8 November 2010 14:59, fmhabash <fmhabash@xxxxxxxxx> wrote:
>>
>>> This is what i got from the default install. the local listeners are
>>> listening on the node vip and public ip. Do we know why?and is it a good
>>> practice to remove the public ip?
>>>
>>> Thank you.
>>> --
>>> //www.freelists.org/webpage/oracle-l
>>>
>>>
>>>
>>
>
>
> --
> Niall Litchfield
> Oracle DBA
> http://www.orawin.info
>
Other related posts:
