Xref: alice comp.databases.oracle.server:33555
Path: alice!news-feed.fnsi.net!news.idt.net!news-peer.gip.net!news.gsl.net!gip.net!newsfeed.cwix.com!206.63.63.70!nwnews.wa.com!brokaw.wa.com!not-for-mail
From: Dan Morgan <dmorgan@exesolutions.com>
Newsgroups: comp.databases.oracle.server
Subject: Re: Index nearing maxextents
Date: Wed, 11 Nov 1998 13:16:38 -0800
Organization: EXE
Lines: 14
Message-ID: <3649FEB6.89DA3CEF@exesolutions.com>
References: <71nttm$pkf$1@supernews.com>
Reply-To: dmorgan@exesolutions.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.06 [en] (WinNT; I)
To: Steve Jaspar <sjaspar@sacbee.com>

> I have an index that is nearing its maxextents. I'm not sure which is the
> best way to handle this:
>
> 1. export and re-import the table
> 2. drop and re-create the index

Drop and recreate the index. And by all means keep the index when you recreate
it to one extent by creating an appropriate storage clause. Even though Oracle
has now made it possible to have effectively unlimited extents this option is
for the lazy that don't care about performance. A good rule of thumb is to never
let the number of extents exceed 20.

Daniel A. Morgan