<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Exadata Bundle Patch 5 Gotcha&#039;s</title>
	<atom:link href="http://blog.enkitec.com/2010/08/exadata-bundle-patch-5-gotchas/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.enkitec.com/2010/08/exadata-bundle-patch-5-gotchas/</link>
	<description>The official blog of Enkitec</description>
	<lastBuildDate>Fri, 09 Dec 2011 11:29:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: Randy Johnson</title>
		<link>http://blog.enkitec.com/2010/08/exadata-bundle-patch-5-gotchas/#comment-164</link>
		<dc:creator>Randy Johnson</dc:creator>
		<pubDate>Tue, 07 Sep 2010 20:06:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enkitec.com/?p=134#comment-164</guid>
		<description>Okay so this morning I figured out what was causing my database startup from SQL Plus to fail after relinking for RDS. It&#039;s a little embarrassing but in all fairness to Oracle I felt I owed them a followup. I also learned something a little interesting about RDS. As you may recall after relinking the oracle kernel so that it uses RDS for Interconnect traffic I started getting the following error when using SQL Plus to startup my database:

   SQL&gt; startup ORA-27504: IPC error creating OSD context

After we finished configuring our Exadata machine I proceeded to configure my shell environment. When I did I copied over my profile script from another server. Well as you might have already guessed I missed resetting a variable to the new server environment. The variable is ORA_CRS_HOME. It was still set to /opt/oracle/... while on our Exadata database servers it is the standard /u01/app/11.2.0/grid. What is interesting about this is that it has never been set properly but it never caused an error during startup using SQL Plus while the databases were using UDP for the Interconnect. It only started causing a problem after I relinked the kernel for RDS.

My thanks to everyone who offered their comments on this post.</description>
		<content:encoded><![CDATA[<p>Okay so this morning I figured out what was causing my database startup from SQL Plus to fail after relinking for RDS. It&#8217;s a little embarrassing but in all fairness to Oracle I felt I owed them a followup. I also learned something a little interesting about RDS. As you may recall after relinking the oracle kernel so that it uses RDS for Interconnect traffic I started getting the following error when using SQL Plus to startup my database:</p>
<p>   SQL> startup ORA-27504: IPC error creating OSD context</p>
<p>After we finished configuring our Exadata machine I proceeded to configure my shell environment. When I did I copied over my profile script from another server. Well as you might have already guessed I missed resetting a variable to the new server environment. The variable is ORA_CRS_HOME. It was still set to /opt/oracle/&#8230; while on our Exadata database servers it is the standard /u01/app/11.2.0/grid. What is interesting about this is that it has never been set properly but it never caused an error during startup using SQL Plus while the databases were using UDP for the Interconnect. It only started causing a problem after I relinked the kernel for RDS.</p>
<p>My thanks to everyone who offered their comments on this post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy Johnson</title>
		<link>http://blog.enkitec.com/2010/08/exadata-bundle-patch-5-gotchas/#comment-163</link>
		<dc:creator>Randy Johnson</dc:creator>
		<pubDate>Wed, 01 Sep 2010 23:55:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enkitec.com/?p=134#comment-163</guid>
		<description>The error seemed to be that Opatch couldn&#039;t copy the new version of dbfs_client to the target directory. The fix was pretty straight forward so I&#039;m not sure why it would affect us and not you but maybe it had to do with the patch level of Oracle we were applying the patch to.</description>
		<content:encoded><![CDATA[<p>The error seemed to be that Opatch couldn&#8217;t copy the new version of dbfs_client to the target directory. The fix was pretty straight forward so I&#8217;m not sure why it would affect us and not you but maybe it had to do with the patch level of Oracle we were applying the patch to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy Johnson</title>
		<link>http://blog.enkitec.com/2010/08/exadata-bundle-patch-5-gotchas/#comment-162</link>
		<dc:creator>Randy Johnson</dc:creator>
		<pubDate>Wed, 01 Sep 2010 23:52:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enkitec.com/?p=134#comment-162</guid>
		<description>Hey Kevin. Here&#039;s the error we got when installing BP5.

The following actions have failed: Copy failed from &#039;/home/oracle/stage/9870547/files/bin/dbfs_client&#039; to &#039;/u01/app/oracle/product/11.2.0/dbhome_1/bin/dbfs_client&#039;...

After checking permissions on the target file and directory I just tried moving the file out of the way and re-trying the step. It executed without any further errors.
I mentioned this in the post so is there anything else I can tell you about our environment that might help?</description>
		<content:encoded><![CDATA[<p>Hey Kevin. Here&#8217;s the error we got when installing BP5.</p>
<p>The following actions have failed: Copy failed from &#8216;/home/oracle/stage/9870547/files/bin/dbfs_client&#8217; to &#8216;/u01/app/oracle/product/11.2.0/dbhome_1/bin/dbfs_client&#8217;&#8230;</p>
<p>After checking permissions on the target file and directory I just tried moving the file out of the way and re-trying the step. It executed without any further errors.<br />
I mentioned this in the post so is there anything else I can tell you about our environment that might help?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yasin Baskan</title>
		<link>http://blog.enkitec.com/2010/08/exadata-bundle-patch-5-gotchas/#comment-161</link>
		<dc:creator>Yasin Baskan</dc:creator>
		<pubDate>Wed, 01 Sep 2010 12:51:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enkitec.com/?p=134#comment-161</guid>
		<description>Hi Randy,

Sorry I could not reply earlier. I did not check if the machine I patches was using RDS, but it should be since the default Exadata installation uses RDS. I have applied BP5 on a system having BP4 and using DBFS with no problems. I have another one that will move to BP5 from BP3 and which is also using DBFS. Let me see how it will go.</description>
		<content:encoded><![CDATA[<p>Hi Randy,</p>
<p>Sorry I could not reply earlier. I did not check if the machine I patches was using RDS, but it should be since the default Exadata installation uses RDS. I have applied BP5 on a system having BP4 and using DBFS with no problems. I have another one that will move to BP5 from BP3 and which is also using DBFS. Let me see how it will go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Closson</title>
		<link>http://blog.enkitec.com/2010/08/exadata-bundle-patch-5-gotchas/#comment-160</link>
		<dc:creator>Kevin Closson</dc:creator>
		<pubDate>Wed, 01 Sep 2010 01:25:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enkitec.com/?p=134#comment-160</guid>
		<description>&gt;I still believe there is a problem with the BP5 install when DBFS is being used but haven’t heard from anyone else on the subject.

...can you be a little more specific?</description>
		<content:encoded><![CDATA[<p>&gt;I still believe there is a problem with the BP5 install when DBFS is being used but haven’t heard from anyone else on the subject.</p>
<p>&#8230;can you be a little more specific?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy Johnson</title>
		<link>http://blog.enkitec.com/2010/08/exadata-bundle-patch-5-gotchas/#comment-159</link>
		<dc:creator>Randy Johnson</dc:creator>
		<pubDate>Tue, 31 Aug 2010 14:25:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enkitec.com/?p=134#comment-159</guid>
		<description>Okay so this week I&#039;m at a client site working on a half rack Exadata and I&#039;m afraid I&#039;m going to  have to eat some crow. Good thing I skipped breakfast today. This client is running Cell OS 11.2.1.2.6 and Oracle 11.2.1.0. The Oracle kernel is configured for RDS over the interconnect so I tried shutting down and restarting their database using sqlplus. The database started without any sign of the RDS bind error I&#039;m seeing back in my lab environment. So this looks like it was a bug in our configuration. I still believe there is a problem with the BP5 install when DBFS is being used but haven&#039;t heard from anyone else on the subject. We&#039;ll be installing BP5 here at this client in the next few days. I&#039;ll followup with a post with my findings.</description>
		<content:encoded><![CDATA[<p>Okay so this week I&#8217;m at a client site working on a half rack Exadata and I&#8217;m afraid I&#8217;m going to  have to eat some crow. Good thing I skipped breakfast today. This client is running Cell OS 11.2.1.2.6 and Oracle 11.2.1.0. The Oracle kernel is configured for RDS over the interconnect so I tried shutting down and restarting their database using sqlplus. The database started without any sign of the RDS bind error I&#8217;m seeing back in my lab environment. So this looks like it was a bug in our configuration. I still believe there is a problem with the BP5 install when DBFS is being used but haven&#8217;t heard from anyone else on the subject. We&#8217;ll be installing BP5 here at this client in the next few days. I&#8217;ll followup with a post with my findings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy Johnson</title>
		<link>http://blog.enkitec.com/2010/08/exadata-bundle-patch-5-gotchas/#comment-158</link>
		<dc:creator>Randy Johnson</dc:creator>
		<pubDate>Fri, 27 Aug 2010 14:15:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enkitec.com/?p=134#comment-158</guid>
		<description>Yasin, thanks for your comment. That is the way I read it too. But like I said since we configured RDS on our Oracle Home and Grid Home we have not been able to start our database using sqlplus. When we do we get the &quot;Could not bind RDS socket&quot; error. Have you verified that you really have RDS configured? How did you verify that? The documentation states that you should see something like &quot;CELL interconnect IPC version: Oracle RDS/IP (generic)&quot; in your database alert log when you startup the database. Would you mind checking and let me know? Like I mentioned in the article, I&#039;m not sure at this point whether or not this is normal behavior for an RDS configured database or if it was some kind of problem with our environment.

On another note are you running DBFS? Did you have any issues with BP5 relating to that?</description>
		<content:encoded><![CDATA[<p>Yasin, thanks for your comment. That is the way I read it too. But like I said since we configured RDS on our Oracle Home and Grid Home we have not been able to start our database using sqlplus. When we do we get the &#8220;Could not bind RDS socket&#8221; error. Have you verified that you really have RDS configured? How did you verify that? The documentation states that you should see something like &#8220;CELL interconnect IPC version: Oracle RDS/IP (generic)&#8221; in your database alert log when you startup the database. Would you mind checking and let me know? Like I mentioned in the article, I&#8217;m not sure at this point whether or not this is normal behavior for an RDS configured database or if it was some kind of problem with our environment.</p>
<p>On another note are you running DBFS? Did you have any issues with BP5 relating to that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yasin Baskan</title>
		<link>http://blog.enkitec.com/2010/08/exadata-bundle-patch-5-gotchas/#comment-156</link>
		<dc:creator>Yasin Baskan</dc:creator>
		<pubDate>Fri, 27 Aug 2010 09:47:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enkitec.com/?p=134#comment-156</guid>
		<description>Hi Randy,

The readme states, &quot;if the applying system is using UDP&quot;. So why not just skip this section as the db machine uses RDS by default?

We had no problems applying the patch if you skip this step. No issues in startup upgrade either.</description>
		<content:encoded><![CDATA[<p>Hi Randy,</p>
<p>The readme states, &#8220;if the applying system is using UDP&#8221;. So why not just skip this section as the db machine uses RDS by default?</p>
<p>We had no problems applying the patch if you skip this step. No issues in startup upgrade either.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kerry Osborne&#8217;s Oracle Blog &#187; Blog Archive Notes on Applying Exadata Bundle Patch (BP5) - Kerry Osborne’s Oracle Blog</title>
		<link>http://blog.enkitec.com/2010/08/exadata-bundle-patch-5-gotchas/#comment-155</link>
		<dc:creator>Kerry Osborne&#8217;s Oracle Blog &#187; Blog Archive Notes on Applying Exadata Bundle Patch (BP5) - Kerry Osborne’s Oracle Blog</dc:creator>
		<pubDate>Thu, 26 Aug 2010 22:44:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enkitec.com/?p=134#comment-155</guid>
		<description>[...] http://blog.enkitec.com/2010/08/25/exadata-bundle-patch-5-gotchas/    Category: Exadata, Oracle &#160;&#124;&#160;&#160;Comment (RSS) &#160;&#124;&#160;&#160;Trackback [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://blog.enkitec.com/2010/08/25/exadata-bundle-patch-5-gotchas/" rel="nofollow">http://blog.enkitec.com/2010/08/25/exadata-bundle-patch-5-gotchas/</a>    Category: Exadata, Oracle &nbsp;|&nbsp;&nbsp;Comment (RSS) &nbsp;|&nbsp;&nbsp;Trackback [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

