Re: switch redo logs off for one table

The answer is no.

If a transaction generates redo (and every normal insert, delete or update always does, regardless of your setting for NOLOGGING), then that redo will be written to the online logs, and online logs get archived, so your transactions are in the archived redo logs.

As someone else has mentioned, you might find that 'create global temporary table BLAH (col1 number, col2 char(5)) etc' fits the bill, as transactions in global temporary tables are never logged... largely because the data inserted into such a table is only visible to the session that put them there.

Alternatives are 'create table BLAH nologging as select * from somewhere_else', or 'insert into BLAH select * from somewhere_else', because those two statements will respect the NOLOGGING attribute (in the second case, only if you've previously done an 'alter table BLAH nologging'.

Regards
HJR "Andrei Romazanov" <romazanov.andrei_at_gfos.de> wrote in message news:atq23l$1fp2j$1_at_ID-70985.news.dfncis.de...
> I meant naturally ARCHIVER-LOGs, not redo logs
>
> Sorry!
>
>
>
Received on Wed Dec 18 2002 - 13:21:41 CST