RE: B-Tree to Partitioned index

Before trying option 2) make sure that none of your applications do a = "select *" from that table, or an "insert into" that table without = explicitly specifying the column list for the insert.=20

-----Original Message-----
From: oracle-l-bounce_at_freelists.org =
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Connor McDonald Sent: mercredi, 29. d=E9cembre 2004 17:07 To: oracle-l_at_freelists.org
Subject: Re: B-Tree to Partitioned index

Some (untried, untested) ideas...

1. Create the new index online with a trailing additional column in it. = This way you get to leave your current index on there until the new one has completed building.
2. Add a new column "X" to the table that is always null. Then same = concept as (1) but using "X" as the additional column. The new index is then "closer" to the = original one in terms of size and (theoretically) its impact on execution plans should be reduced.=20
3. If your table is partitioned and your new index is going to be = locally partitioned, check out DBMS_PCLXUTIL for some nice ways of building the index in a = time-efficient manner.

hth
connor

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