<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Intermittent ORA-12545 When Trying To Connect To RAC Database</title>
	<link>http://www.davidyahalom.com/index.php/intermittent-ora-12545-when-trying-to-connect-to-rac-database/</link>
	<description>Innovative Integration</description>
	<pubDate>Sun, 05 Feb 2012 00:02:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>By: Evil Genius</title>
		<link>http://www.davidyahalom.com/index.php/intermittent-ora-12545-when-trying-to-connect-to-rac-database/#comment-24697</link>
		<author>Evil Genius</author>
		<pubDate>Thu, 15 Apr 2010 08:04:15 +0000</pubDate>
		<guid>http://www.davidyahalom.com/index.php/intermittent-ora-12545-when-trying-to-connect-to-rac-database/#comment-24697</guid>
		<description>Hi, 

We've finally solved this behaviour following the metakink note: How To Configure Dispatchers For RAC Environment [ID 578524.1]

"Note: It is very important to use entire address string in order to configure dispatchers on RAC and host name used in it should be a VIP hostname, otherwise connection may suffer intermittent ORA-12545 errors. Refer metalink note &#62;"

The solution was to set the parameter DISPATCHERS on every node of the cluster pointing to the node-vip as a connection string:

{noformat}
alter system set dispatchers='(address=(protocol=tcp)(host=$HOSTNAME-vip)) (dispatchers=2)' scope=both sid='$ORACLE_SID';
{noformat}

Regards, 

Enric Moya</description>
		<content:encoded><![CDATA[<p>Hi, </p>
<p>We&#8217;ve finally solved this behaviour following the metakink note: How To Configure Dispatchers For RAC Environment [ID 578524.1]</p>
<p>&#8220;Note: It is very important to use entire address string in order to configure dispatchers on RAC and host name used in it should be a VIP hostname, otherwise connection may suffer intermittent ORA-12545 errors. Refer metalink note &gt;&#8221;</p>
<p>The solution was to set the parameter DISPATCHERS on every node of the cluster pointing to the node-vip as a connection string:</p>
<p>{noformat}<br />
alter system set dispatchers=&#8217;(address=(protocol=tcp)(host=$HOSTNAME-vip)) (dispatchers=2)&#8217; scope=both sid=&#8217;$ORACLE_SID&#8217;;<br />
{noformat}</p>
<p>Regards, </p>
<p>Enric Moya</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Norris</title>
		<link>http://www.davidyahalom.com/index.php/intermittent-ora-12545-when-trying-to-connect-to-rac-database/#comment-53</link>
		<author>Dan Norris</author>
		<pubDate>Wed, 23 Jul 2008 13:43:33 +0000</pubDate>
		<guid>http://www.davidyahalom.com/index.php/intermittent-ora-12545-when-trying-to-connect-to-rac-database/#comment-53</guid>
		<description>Are you saying that there are times when database clients do not need to resolve DNS names? I always expect that some sort of name resolution is present on all database clients. If there's a problem, it's usually that DNS entries weren't created or were created incorrectly.</description>
		<content:encoded><![CDATA[<p>Are you saying that there are times when database clients do not need to resolve DNS names? I always expect that some sort of name resolution is present on all database clients. If there&#8217;s a problem, it&#8217;s usually that DNS entries weren&#8217;t created or were created incorrectly.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

