Re: rollback space

On 2 Feb 2005 10:39:43 -0800, manish.nevrekar_at_gmail.com wrote:

>1) Each row has 10 columns. Approximately 70 B each row.
>2) No lobs
>3)No other transactions are running, this is a batch load, any other
>transaction if running at all is select.
>4) there are no on isert triggers on the table.
>
>I beg to differ on commiting after every 'x' rows. I always prefer to
>commit once at the end of the transaction. Commiting often is
>definitely more work plus there is always the chance of the dreaded
>ORA-01555 "Snapshot too old" error.
>In my ETL procedures every insert and update is time stamped and hence
>it can be identified.
>Thanks
>Manish

Seems like a case for logminer. Be aware though, as soon as a block needs to be reorganized -and as far as I know rows are always stored adjacent- pretty much the whole block could need to be rewritten.

Logminer will identify the actual insert including the redo size, and any 'internal' operations associated with the SCN, usually index manipulations.

--
Sybrand Bakker, Senior Oracle DBA