On Fri, 13 Apr 2001, Feng, Jun wrote:
> We have that kind application running on the production and didn't have any
> problem since it was deployed last Oct.. The application will truncate the
> one of the table partitions which contains 99% of the data (about 7M
> records) before reload the data every two weeks. For you situation, you can
> truncate partition then drop it. It is easy, clean and quick.
>
Don't forget to recreate/rebuild the indexes - when you truncate or drop a
partition, it places the indexes into an unusable state.
FWIW, I haven't had any problems dropping full partitions - it's quicker than a
truncate/drop (since the same number of extents need to be deallocated, letting
drop clean up the extents is quicker than typing in 'alter table truncate
partition foo;', 'alter table drop partition foo').
Cheers,
GC
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Gregory Conron
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).
