Re: Redo killer

If you want to almost completely eliminate REDO during a load, do the following

1.) Set the table to NOLOGGING
2.) Drop the table indexes (if there are any)
3.) Modify the INSERT statement with the APPEND hint
4.) After table is loaded, rebuild the indexes.

The downside to this is that if the instance fails, there is no recovery for this table.

Alternately, if you cannot drop the indexes, you can save about 30% on REDO by NOLOGGING the table and sending the APPEND hint in the INSERT statement.

RSL "Mike Moore" <mmoore_gmp_at_yahoo.com> wrote in message news:43c454d1.0410251150.21c990eb_at_posting.google.com...
> Part of our billing process creates over 1 million inserts into a
> table which kills our redo logs. Then when the process is complete
> the data is extracted and never referenced again. We truncate the
> table each night. In other words the data is semi-temporary.
>
> I'd change the table definition to a temporary table, except that if
> the program crashes it needs to pick up where it left off and not
> start all over again. There has got to be another way to handle this
> process, but I'm at a loss for a solution. Any ideas would be greatly
> appreciated!!!
Received on Thu Oct 28 2004 - 03:26:14 CDT