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

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.

By: Yuri

Yuri — Fri, 18 Sep 2009 15:02:51 +0000

What about dispatcher registration?
I have problem with it.

…
Service “iadbu” has 8 instance(s).
Instance “iadbu1″, status READY, has 3 handler(s) for this service…
Handler(s):
“DEDICATED” established:0 refused:0 state:ready
REMOTE SERVER
(ADDRESS=(PROTOCOL=TCP)(HOST=srv1p0-vip)(PORT=1521))
“DEDICATED” established:0 refused:0 state:ready
LOCAL SERVER
“D000″ established:0 refused:0 current:3 max:1022 state:ready
DISPATCHER
(ADDRESS=(PROTOCOL=tcp)(HOST=srv1p0)(PORT=60556))
Instance “iadbu2″, status READY, has 2 handler(s) for this service…
Handler(s):
“D000″ established:0 refused:0 current:2 max:1022 state:ready
DISPATCHER
(ADDRESS=(PROTOCOL=tcp)(HOST=srv1p1)(PORT=15729))
“DEDICATED” established:0 refused:0 state:ready
REMOTE SERVER
(ADDRESS=(PROTOCOL=TCP)(HOST=srv1p1-vip)(PORT=1521))
…

By: Pythian Video: Oracle RAC VIP’s — Troubleshooting Connectivity Issues | Pythian Group Blog

Mon, 27 Jul 2009 06:18:40 +0000

[...] 1 — Pythian Video: Oracle RAC — VIP Configuration Mistakes 2 — Pythian Video: Oracle RAC — Why VIPs? [...]

By: Surachart Opun

Surachart Opun — Fri, 10 Jul 2009 10:14:15 +0000

Thank you, Alex ;)

this’s a great job and helpful.