It doesn't even store the rowid really,
just an instruction to eliminate a row
index entry in a table block. However
the basic infrastructure of undo (rollback)
requires about 80 bytes overhead per
undo record - so your 680MB for 10M
single row inserts is a bit on the small
side.
--
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk
Next Seminar dates:
(see http://www.jlcomp.demon.co.uk/seminar.html )
____USA__________November 7/9 (MI), 19/21 (TX)
____England______November 12/14
The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
charlie cs wrote in message ...
>too much rollback segment usage
>
>I was doing
>SQL> desc test
>Name Null? Type
>----------------------------------------- -------- ------------------------
-
>---
>DASET_ID NOT NULL NUMBER(10)
>SECT_ID NOT NULL NUMBER(10)
>
>begin
>for i in 1 .. 10000000 loop
>insert into test values (i,1);
>end loop;
>commit;
>end;
>/
>PL/SQL procedure successfully completed.
>
>After it finish, the highwater mark of table is only 150M, but during the
>inserts, rollback segments grow up to 680M, why do we need such a big
>rollback segments for such a small table? According to some OCP book,
>insert only store new rowid into the rollback segments.
>
>Thanks for your help.
>
>by the way, there is no indexes on the table
>
>
>
Received on Tue Oct 01 2002 - 21:21:59 CDT
