Re: Rollback extents

From: Richard Foote <richard.foote_at_bigpond.com>
Date: Thu, 27 Jun 2002 18:42:32 +1000
Message-ID: <e6AS8.22077$Hj3.69261@newsfeeds.bigpond.com>

Note that the rollback segment holds the previous value of the row which in the case of an insert is the rowid plus overhead. So you wouldn't expect the rollback segment to reach 3-8 Gigs in size.

nologging would not solve the problem as it only suppresses the generation of redo not undo.

The rollback is used for rollback, recovery and read consistency, any of which may be necessary.

Regards

Richard
"nilanjan" <nilanjan_sarkar_at_hotmail.com> wrote in message news:6c8b1f5.0206261454.760b80a7_at_posting.google.com...
> Per the math involved here, the # extents multipled by extent size in
> yr case is 500*320K=160Megabytes ...which is wayyy smaller than your
> single load of 3-8 Gigabytes !!!
>
> Would be interesting to find if NOLOGGING resolves yr problem.
>
> BTW: thinking about the rollback stuff, basic question, any comments
> on why would Oracle need rollback ( not REDO) for an INSERT or SELECT
> ??
Received on Thu Jun 27 2002 - 03:42:32 CDT