<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ALTER INDEX on Oracle Scripts</title><link>https://www.oraclescripts.com/tags/alter-index/</link><description>Recent content in ALTER INDEX on Oracle Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>OracleScripts.com</copyright><lastBuildDate>Sat, 06 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.oraclescripts.com/tags/alter-index/index.xml" rel="self" type="application/rss+xml"/><item><title>Oracle Index Rebuild and Coalesce with ALTER INDEX</title><link>https://www.oraclescripts.com/post/oracle-index-rebuild-coalesce-alter-index/</link><pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.oraclescripts.com/post/oracle-index-rebuild-coalesce-alter-index/</guid><description>
&lt;h2 id="oracle-index-rebuild-and-coalesce-with-alter-index"&gt;Oracle Index Rebuild and Coalesce with ALTER INDEX&lt;/h2&gt;
&lt;h2 id="purpose"&gt;Purpose&lt;/h2&gt;
&lt;p&gt;Over months of heavy delete and update activity, a B-tree index can accumulate empty and half-full leaf blocks. The index keeps working, but it grows wider than the data it points to, so range scans read more blocks than they need and the segment holds space that is no longer doing useful work. &lt;code&gt;ALTER INDEX ... REBUILD&lt;/code&gt; and &lt;code&gt;ALTER INDEX ... COALESCE&lt;/code&gt; are the two commands that address this — one rebuilds the index from scratch, the other merges adjacent sparse leaf blocks in place.&lt;/p&gt;</description></item></channel></rss>