RE: Deletion Of 160 Million Rows.

It is not just a matter of following asktom advices, it is also about understanding what you cause in production systems with your actions. Usually I am constrained to reducing downtime/locking risks to the minimum. If an auditing table gets updated all the time by the whole user community all over the world 24*7 it requires careful design to achieve the no downtime goal.

Regards,
Andre van Winssen

-----Oorspronkelijk bericht-----
Van: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] Namens ryan_gaffuri_at_comcast.net
Verzonden: dinsdag 8 februari 2005 17:16 Aan: wbfergus_at_usgs.gov; oracle-l_at_freelists.org CC: William B Ferguson
Onderwerp: RE: Deletion Of 160 Million Rows.

create table as nologging is the tried and true best way to do handle this. i believe its tom kytes recommended way of handling this also on asktom. -------------- Original message --------------

> This depends on your application, but another way might be as follows:
>
> 1. Copy your table to another area.
> 2. Truncate your original table (truncate is much faster without the =
> undo
> problem).
> 3. Insert into the original table from the copy for the records you want
> to keep.

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

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