Comments on: Pythian Video: Oracle RAC — VIP Configuration Mistakes

By: Amir Riaz

Amir Riaz — Sun, 12 Jun 2011 11:15:26 +0000

I really like this style of pythian. videos are much easy to learn.

By: odenysenko

odenysenko — Thu, 21 Apr 2011 14:26:51 +0000

Alex,

>>Would dispatchers recover then VIP is moved back?

I have tested and there is nothing unusual:
1) VIP failback – manual or auto, if configured
2) LISTENER will start
3) new DISPATCHER(D001) started
4) after some time PMON will register services with LISTENER,
including local DISPATCHERs
so infrastructure will function as before VIP relocation

I have tested it with 10.2.0.4,
but the same have to be in later releases.

Oleksandr

By: Vladimir Bazanov

Vladimir Bazanov — Fri, 26 Nov 2010 17:35:15 +0000

Thanks a lot for clear description of the problem & ways to fix it. I am quite novice in Oracle, but was able to do all steps succesfully. Later, already knowing what to search, I was able to find direct reference to manual configuring the local_listener parameter in documentation (http://download.oracle.com/docs/cd/B28359_01/install.111/b28264/undrstnd.htm#RILIN006) but without your article it seems to be impossible. Thanks again.

By: Raj

Raj — Wed, 04 Nov 2009 14:27:51 +0000

“Another approach would be to use only real IP’s for remote/local listener registration and in client’s TNS descriptors. This would help to avoid the name resolution problem all together”

Wouldn’t that defeat the purpose of using VIP’s and all the advantage which using VIP’s give?

By: Alex Gorbachev

Alex Gorbachev — Fri, 25 Sep 2009 00:12:13 +0000

I would think Oleksandr is correct but I would like to research what happens when VIP fails temporary and is moved to another node and back. In the early version of CRS, there was dependency of a database instance on the node’s VIP but it was removed in later releases. So if VIP is relocated to “non-native” node then instance is still up. Would dispatchers recover then VIP is moved back?

By: odenysenko

odenysenko — Thu, 24 Sep 2009 08:13:36 +0000

Specify HOST parameter for DISPATCHERS
and DO NOT specify LISTENER.

See
http://odenysenko.wordpress.com/2009/09/24/rac-correct-dispatchers-configuration-no-more-ora-12545/

Oleksandr

By: Yuri

Yuri — Tue, 22 Sep 2009 09:55:23 +0000

Sorry, second choice is dispatchers=’(protocol=TCP)(listener=LOCAL_LISTENER)’

By: Yuri

Yuri — Tue, 22 Sep 2009 09:53:46 +0000

Ok, but I have confused with dispatchers parameter configuration.
If I set it onto dispatchers=’(protocol=TCP)’ and hosts file on client-side not contain resolving for public IP-adresses
then I receive ORA=12545 when attempt to connect with database.
If I set dispatchers=’(protocol=TCP)(listener=)’ then connection is successful, but server-side load balancing is absent.
And if I set back dispatchers=’(protocol=TCP)’ and add public IP-adresses into client-side hosts file then connection and server-side load balansing work fine.
Does last manner is a right way for configuration of connect through dispatcher?

By: Alex Gorbachev

Alex Gorbachev — Mon, 21 Sep 2009 12:54:13 +0000

@Yuri: Thanks for update. Good point about dispatchers indeed. Can you post here you dispatcher configuration?

By: Yuri

Yuri — Mon, 21 Sep 2009 10:35:53 +0000

Oh, sorry, it is not a problem already. I have misconfigured “dispatchers” parameter.