Re: Avoiding redo log for temporary data

From: Richard Woods <rawoods_at_concentric.net>
Date: 1996/08/30
Message-ID: <3227A33A.BE9_at_concentric.net>#1/1


Chris White wrote:
>
> Does anyone know if I can avoid populating the redo log for specific
> transactions? I have a transaction that creates a large amounts of
> temporary rows then deletes them. This is filling up the redo/archive
> logs at an alarming rate. Is there the concept of a temporary table
> (like Sybase)? Or is there a session variable I could toggle?Chris,

You can't selectively disable redo generation by transaction, except when using SQL*Loader in the Unrecoverable mode, or CTAS (create table as select) which has a variation of same.

The alternative is to run your transaction while no one else in logged on, and you've temporarily disabled Archivelog mode, as long as you understand the consequences of doing this (no point in time recovery after media failure.) I don't recommend it, but it is an option.

-- 
Rich Woods
Technical Field Support Specialist, Oracle Corporation, USA
The above statements and opinions are my own and do not
necessarily represent those of Oracle Corporation.
Received on Fri Aug 30 1996 - 00:00:00 CEST

Original text of this message