Re: Please a parameter to disable undo, like _disable_logging

  • From: Tim Gorman <tim@xxxxxxxxxxxxx>
  • To: <oracle-l@xxxxxxxxxxxxx>
  • Date: Tue, 05 Oct 2004 22:18:32 -0600

Direct-path or APPEND inserts do avoid undo, except for the space-management
stuff in the data dictionary.

Direct-path loads data into TEMPORARY segments which, upon successful
completion of the load (a.k.a. commit), are converted into DATA segments.
Upon unsuccessful completion of the load (a.k.a. rollback), the TEMPORARY
segments are simply dropped.

Look ma, no undo...



on 10/5/04 9:33 PM, John Clarke at jclarke@xxxxxxxxxxxxxxx wrote:

> /*+ append */ disables redo, not undo (as does =5Fdisable=5Flogging).
> 
> Array/bulk inserts will reduce the amount of undo you generate, so this =
> method will help.  But you can't avoid undo altogether.
> 
> At least you're not updating or deleting the 10,000,000 rows.
> 
> John
> 
> ----- Original Message -----
> From: Juan Carlos Reyes Pacheco <jreyes@xxxxxxxxxxxxxxxx>
> To: oracle-l@xxxxxxxxxxxxx
> Sent: Tue,  5 Oct 2004 20:23:01 -0400
> Subject: RE: Please a parameter to disable undo, like =5Fdisable=5Floggi=
> ng
> 
> 
>> thanks
>> =20
>> but /*+ append */ too bypasses undo, and if you set =5Fdisable=5Floggi=
> ng you run
>> the same risk, if you have a problem.
>> I think for a test database could be acceptable. For example I'm tryin=
> g to
>> create a 10 000 000 records in my home for testing
>> purposes, so this will be greatly welcome.
>> I bet there should be a way.
>> =20
>> =20
>> Juan Carlos Reyes Pacheco
>> OCP

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

Other related posts: