Re: Rollback extents

"Steve Ashmore" <sashmore_at_neonramp.com> wrote in message news:<uhmv3r9c783o00_at_corp.supernews.com>...
> That is what I get for working on this at 5AM.
>
> Nologging is of course for used to suspend redo generation.
>
> Interesting though. If you do a direct load insert
> you can still issue a rollback and at least some
> rollback information is generated. I was playing with this today.
>

DMLs all generate undo, because they can all be rolled back unless you set autocommit to true. I have yet to see an exception.

> Niall , thanx for keeping me honest.
>
> Steve
>
> "Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message
> news:3d19c892$0$225$ed9e5944_at_reading.news.pipex.net...
> > "Steve Ashmore" <sashmore_at_neonramp.com> wrote in message
> > news:uhj77gl5qg0098_at_corp.supernews.com...
> > > As Mr Kyte recently point out, the table must be in
> > > Nologging mode in order not to generate
> > > REDO or rollback when using the APPEND Hint.
> >
> > Nologging applies to redo not to rollback/undo. My understanding (and
> > admittedly you've now made me question it) is that *undo* is skipped on
> > direct load. In anycase there is nothing to stop you altering the table
> > nologging before a batch load of this type assuming you'll take a backup
> > afterward.
> >
> >
> > --
> > Niall Litchfield
> > Oracle DBA
> > Audit Commission UK
> > *****************************************
> > Please include version and platform
> > and SQL where applicable
> > It makes life easier and increases the
> > likelihood of a good answer
> >
> > ******************************************
> >
> >
Received on Thu Jun 27 2002 - 22:04:41 CDT