Gregory,
However, if I have a locally partitioned index,
the impact on indexes should be minimized.
I believe that I should only have to rebuild the
index on the next highest partition. The remainder
of the local index partitions should be unaffected.
Am I correct in my understanding of the documentation
on local index partitions?
Thanks,
Cherie
Gregory Conron
<[EMAIL PROTECTED] To: [EMAIL PROTECTED],
[EMAIL PROTECTED]
ndara.com> cc:
Subject: Re: How does dropping a
partition affect the rest of the
04/13/01 05:00 table?
PM
On Fri, 13 Apr 2001, [EMAIL PROTECTED] wrote:
> I've looked through the on-line documentation on dropping partitions
> but I have not seen the following question specifically addressed:
>
> How does dropping a date-range partition affect the rest of the
> table/partitions?
New data will be inserted into the next-highest partition. Current data in
the
partition will be lost.
> Can I drop an unneeded partition on the fly? What is the
> effect on performance of the rest of the table? Does anything
> need to be brought offline before I drop the desired partition?
The hit will be in rebuilding the indexes. Unless you have a large number
of
extents in the partition, it will drop very quickly - quick enough not to
be
noticeable unless a user is running a query or transaction against the data
in
the partition (the query/transaction will fail).
Cheers,
GC
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
