RE: Running time of index rebuild

From: Powell, Mark <mark.powell2_at_hp.com>
Date: Wed, 5 Jun 2013 18:40:49 +0000
Message-ID: <1E24812FBE5611419EFAFC488D7CCDD1186C5954_at_G6W2491.americas.hpqcorp.net>


Before rebuilding or drop/re-create of large indexes it is a good idea to compare the size of the index to the amount of temporary tablespace available. Over the last 20 years I have encountered a couple of cases where the indexes outgrew the temp allocation. This is not something you want to find out after you have dropped the index.

-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of rjamya Sent: Wednesday, June 05, 2013 2:00 PM
To: giantpanda_at_gmx.net
Cc: ORACLE-L
Subject: Re: Running time of index rebuild

I may be wrong, but wouldn't you need a whole new temporary segment for rebuild in addition to existing index? so you might actually use more space until rebuild operation is complete. And if you have maintenance window, why not just drop old one and re-create? So the new index will reuse recently freed space as well? Raj

On Wed, Jun 5, 2013 at 10:56 AM, Ingrid Voigt <giantpanda_at_gmx.net> wrote:

> My suggestion for the maintenance window prod would be 16 hours, do
> you have a better idea?

--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l
Received on Wed Jun 05 2013 - 20:40:49 CEST

Original text of this message