<?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: Moving Oracle Datafiles to a ZFS Filesystem with the Correct Recordsize</title>
	<atom:link href="http://www.pythian.com/news/3627/moving-oracle-datafiles-to-a-zfs-filesystem-with-the-correct-recordsize/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pythian.com/news/3627/moving-oracle-datafiles-to-a-zfs-filesystem-with-the-correct-recordsize/</link>
	<description>News and views from Pythian DBAs</description>
	<lastBuildDate>Thu, 18 Mar 2010 23:57:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Don Seiler</title>
		<link>http://www.pythian.com/news/3627/moving-oracle-datafiles-to-a-zfs-filesystem-with-the-correct-recordsize/#comment-390013</link>
		<dc:creator>Don Seiler</dc:creator>
		<pubDate>Thu, 03 Dec 2009 21:48:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/news/?p=3627#comment-390013</guid>
		<description>Michael, you can do it with UNDO.  Simply create a new UNDO tablespace in the new ZFS mount.  Then change the system undo setting.  Wait for all operations to use the new UNDO and you&#039;ll be able to drop the old one.

This is precisely what I did, same goes for TEMP.</description>
		<content:encoded><![CDATA[<p>Michael, you can do it with UNDO.  Simply create a new UNDO tablespace in the new ZFS mount.  Then change the system undo setting.  Wait for all operations to use the new UNDO and you&#8217;ll be able to drop the old one.</p>
<p>This is precisely what I did, same goes for TEMP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.pythian.com/news/3627/moving-oracle-datafiles-to-a-zfs-filesystem-with-the-correct-recordsize/#comment-390001</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Thu, 03 Dec 2009 21:08:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/news/?p=3627#comment-390001</guid>
		<description>What you are suggesting here will not work for system level tablespaces such as SYSTEM, SYSAUX, UNDO.  These will require the entire database to be down to move.  They cannot be taken offline while the database is running.  You&#039;d still have a database outage!

Also, taking individual datafiles offline in a running system can cause logical data problems which might not be immediately recognizable in an high-throughput application with referential integrity.  For example, you could generate an order record in one tablespace, and then, when attempting to assign the order to a customer in an offline tables, you could end up with an orphaned order.

We are encountering this same issue right now.  Luckily, the system is not live yet.  Good articles such as yours led us to decide to change the ZFS recordsize before we went live (thank goodness)!!!</description>
		<content:encoded><![CDATA[<p>What you are suggesting here will not work for system level tablespaces such as SYSTEM, SYSAUX, UNDO.  These will require the entire database to be down to move.  They cannot be taken offline while the database is running.  You&#8217;d still have a database outage!</p>
<p>Also, taking individual datafiles offline in a running system can cause logical data problems which might not be immediately recognizable in an high-throughput application with referential integrity.  For example, you could generate an order record in one tablespace, and then, when attempting to assign the order to a customer in an offline tables, you could end up with an orphaned order.</p>
<p>We are encountering this same issue right now.  Luckily, the system is not live yet.  Good articles such as yours led us to decide to change the ZFS recordsize before we went live (thank goodness)!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Moving Oracle Datafiles to a ZFS Filesystem with the Correct Recordsize &#171; die Seilerwerks</title>
		<link>http://www.pythian.com/news/3627/moving-oracle-datafiles-to-a-zfs-filesystem-with-the-correct-recordsize/#comment-380521</link>
		<dc:creator>Moving Oracle Datafiles to a ZFS Filesystem with the Correct Recordsize &#171; die Seilerwerks</dc:creator>
		<pubDate>Sat, 24 Oct 2009 16:20:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/news/?p=3627#comment-380521</guid>
		<description>[...] leave a comment &#187;  Originally posted on The Pythian Group blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] leave a comment &raquo;  Originally posted on The Pythian Group blog. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blogroll Report 14/08/2009 – 21/08/2009 &#171; Coskan&#8217;s Approach to Oracle</title>
		<link>http://www.pythian.com/news/3627/moving-oracle-datafiles-to-a-zfs-filesystem-with-the-correct-recordsize/#comment-373867</link>
		<dc:creator>Blogroll Report 14/08/2009 – 21/08/2009 &#171; Coskan&#8217;s Approach to Oracle</dc:creator>
		<pubDate>Mon, 07 Sep 2009 16:41:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/news/?p=3627#comment-373867</guid>
		<description>[...] 10 &#8211; Using backup copy to move files after changing the recordsize on filesystem ?  Don Seiler-Moving Oracle Datafiles to a ZFS Filesystem with the Correct Recordsize [...]</description>
		<content:encoded><![CDATA[<p>[...] 10 &#8211; Using backup copy to move files after changing the recordsize on filesystem ?  Don Seiler-Moving Oracle Datafiles to a ZFS Filesystem with the Correct Recordsize [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don Seiler</title>
		<link>http://www.pythian.com/news/3627/moving-oracle-datafiles-to-a-zfs-filesystem-with-the-correct-recordsize/#comment-370686</link>
		<dc:creator>Don Seiler</dc:creator>
		<pubDate>Thu, 20 Aug 2009 14:56:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/news/?p=3627#comment-370686</guid>
		<description>Peter: That&#039;s why you have to run the &quot;recover datafile X&quot; command after the switch and before putting the new copy online.</description>
		<content:encoded><![CDATA[<p>Peter: That&#8217;s why you have to run the &#8220;recover datafile X&#8221; command after the switch and before putting the new copy online.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Moore</title>
		<link>http://www.pythian.com/news/3627/moving-oracle-datafiles-to-a-zfs-filesystem-with-the-correct-recordsize/#comment-370679</link>
		<dc:creator>Peter Moore</dc:creator>
		<pubDate>Thu, 20 Aug 2009 14:38:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/news/?p=3627#comment-370679</guid>
		<description>Hello.

Great article with some interesting ideas.

One question though:  Is there not the possibility that the datafile is being written to while the &quot;backup as copy&quot; is running (and until the point when the file is taken offline)?

How do we ensure that the *new* copy of the file is up-to-date?</description>
		<content:encoded><![CDATA[<p>Hello.</p>
<p>Great article with some interesting ideas.</p>
<p>One question though:  Is there not the possibility that the datafile is being written to while the &#8220;backup as copy&#8221; is running (and until the point when the file is taken offline)?</p>
<p>How do we ensure that the *new* copy of the file is up-to-date?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
