<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Fragmentation 4</title>
	<atom:link href="http://jonathanlewis.wordpress.com/2010/07/22/fragmentation-4/feed/" rel="self" type="application/rss+xml" />
	<link>http://jonathanlewis.wordpress.com/2010/07/22/fragmentation-4/</link>
	<description>Just another Oracle weblog</description>
	<lastBuildDate>Sat, 18 May 2013 11:04:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Vikram Rathour</title>
		<link>http://jonathanlewis.wordpress.com/2010/07/22/fragmentation-4/#comment-44940</link>
		<dc:creator><![CDATA[Vikram Rathour]]></dc:creator>
		<pubDate>Mon, 06 Feb 2012 05:06:15 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanlewis.wordpress.com/?p=4154#comment-44940</guid>
		<description><![CDATA[Hi Jonathan,

I have been following your blogs very regularly and they have always been very insightful. Offlate we have a debate going on internally withing a bunch of DB professionals and we are trying to identify what exactly drives organizations to migrate from one DB to another. In this one of the DB2 professional sent me a link:

http://www.gartner.com/resources/167700/167786/ibm_db2_97_shakes_up_the_dbm_167786.pdf

and it really appalled me to see that a huge org like IBM is adopting a startegy to go after Oracle rather than come with something good of their own. 

I have just started reading your book Oracle Core... and I think chapter 02 should really end this debate.
What are your thoughts?


Note: My apologies if I have posted this in the wrong place...but I could not really find a right post to put this query through

Regards,
Vikram R]]></description>
		<content:encoded><![CDATA[<p>Hi Jonathan,</p>
<p>I have been following your blogs very regularly and they have always been very insightful. Offlate we have a debate going on internally withing a bunch of DB professionals and we are trying to identify what exactly drives organizations to migrate from one DB to another. In this one of the DB2 professional sent me a link:</p>
<p><a href="http://www.gartner.com/resources/167700/167786/ibm_db2_97_shakes_up_the_dbm_167786.pdf" rel="nofollow">http://www.gartner.com/resources/167700/167786/ibm_db2_97_shakes_up_the_dbm_167786.pdf</a></p>
<p>and it really appalled me to see that a huge org like IBM is adopting a startegy to go after Oracle rather than come with something good of their own. </p>
<p>I have just started reading your book Oracle Core&#8230; and I think chapter 02 should really end this debate.<br />
What are your thoughts?</p>
<p>Note: My apologies if I have posted this in the wrong place&#8230;but I could not really find a right post to put this query through</p>
<p>Regards,<br />
Vikram R</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Book Review: Oracle Database 11g Performance Tuning Recipes (Part 2) &#171; Charles Hooper&#039;s Oracle Notes</title>
		<link>http://jonathanlewis.wordpress.com/2010/07/22/fragmentation-4/#comment-41972</link>
		<dc:creator><![CDATA[Book Review: Oracle Database 11g Performance Tuning Recipes (Part 2) &#171; Charles Hooper&#039;s Oracle Notes]]></dc:creator>
		<pubDate>Thu, 06 Oct 2011 06:07:36 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanlewis.wordpress.com/?p=4154#comment-41972</guid>
		<description><![CDATA[[...] has become fragmented over time.”  The book does not describe what it means for an index to be fragmented and does not describe some of the potential unanticipated side-effects of parallel index rebuilds [...]]]></description>
		<content:encoded><![CDATA[<p>[...] has become fragmented over time.”  The book does not describe what it means for an index to be fragmented and does not describe some of the potential unanticipated side-effects of parallel index rebuilds [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fragmentation 1 &#171; Oracle Scratchpad</title>
		<link>http://jonathanlewis.wordpress.com/2010/07/22/fragmentation-4/#comment-37217</link>
		<dc:creator><![CDATA[Fragmentation 1 &#171; Oracle Scratchpad]]></dc:creator>
		<pubDate>Mon, 06 Sep 2010 13:00:25 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanlewis.wordpress.com/?p=4154#comment-37217</guid>
		<description><![CDATA[[...] Index Fragmentation [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Index Fragmentation [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Lewis</title>
		<link>http://jonathanlewis.wordpress.com/2010/07/22/fragmentation-4/#comment-36837</link>
		<dc:creator><![CDATA[Jonathan Lewis]]></dc:creator>
		<pubDate>Sat, 24 Jul 2010 10:51:27 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanlewis.wordpress.com/?p=4154#comment-36837</guid>
		<description><![CDATA[Narendra,

The example that Richard gives in that article is demonstrating a particular special case - if you delete and reinsert a unique key (protected by a unique index) within the single transaction, the index entry is marked as deleted, and then the delete flag is cleared so the index entry is immediately re-used.

In the more general case, if your transaction deletes one index entry from a unique index and inserts a different value (and it&#039;s one that is so close to the original that it should go in the same block) then the space from the deleted entry will not be available for reuse.]]></description>
		<content:encoded><![CDATA[<p>Narendra,</p>
<p>The example that Richard gives in that article is demonstrating a particular special case &#8211; if you delete and reinsert a unique key (protected by a unique index) within the single transaction, the index entry is marked as deleted, and then the delete flag is cleared so the index entry is immediately re-used.</p>
<p>In the more general case, if your transaction deletes one index entry from a unique index and inserts a different value (and it&#8217;s one that is so close to the original that it should go in the same block) then the space from the deleted entry will not be available for reuse.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blogroll Report 16/07/2010 – 23/07/2010 &#171; Coskan&#8217;s Approach to Oracle</title>
		<link>http://jonathanlewis.wordpress.com/2010/07/22/fragmentation-4/#comment-36824</link>
		<dc:creator><![CDATA[Blogroll Report 16/07/2010 – 23/07/2010 &#171; Coskan&#8217;s Approach to Oracle]]></dc:creator>
		<pubDate>Fri, 23 Jul 2010 15:17:49 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanlewis.wordpress.com/?p=4154#comment-36824</guid>
		<description><![CDATA[[...] 3-What is index level fragmentation? Jonathan Lewis-Fragmentation-4 [...]]]></description>
		<content:encoded><![CDATA[<p>[...] 3-What is index level fragmentation? Jonathan Lewis-Fragmentation-4 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Narendra</title>
		<link>http://jonathanlewis.wordpress.com/2010/07/22/fragmentation-4/#comment-36816</link>
		<dc:creator><![CDATA[Narendra]]></dc:creator>
		<pubDate>Fri, 23 Jul 2010 09:41:56 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanlewis.wordpress.com/?p=4154#comment-36816</guid>
		<description><![CDATA[&lt;i&gt;when Oracle deletes a row from an index it has to leave the entire index entry in place and flag it as deleted – it cannot immediately reuse the space, it has to wait until after the commit. (I posted an example demonstrating this difference a few months ago.)&lt;/i&gt;
I think not reusing the space part is only applicable to non-unique indexes. Unique indexes reuse space within same transaction.
http://richardfoote.wordpress.com/2009/03/25/differences-between-unique-and-non-unique-indexes-part-iv-take-it-back/]]></description>
		<content:encoded><![CDATA[<p><i>when Oracle deletes a row from an index it has to leave the entire index entry in place and flag it as deleted – it cannot immediately reuse the space, it has to wait until after the commit. (I posted an example demonstrating this difference a few months ago.)</i><br />
I think not reusing the space part is only applicable to non-unique indexes. Unique indexes reuse space within same transaction.<br />
<a href="http://richardfoote.wordpress.com/2009/03/25/differences-between-unique-and-non-unique-indexes-part-iv-take-it-back/" rel="nofollow">http://richardfoote.wordpress.com/2009/03/25/differences-between-unique-and-non-unique-indexes-part-iv-take-it-back/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
