Re: TRUNCATE and ARCHIVELOG mode

I think

ALTER TABLE .. NOLOGGING should do.

Ingo

Keith E. Moore wrote:

> Sorry to hop on to your post, but I have a similar question for the
> oposite reason:
>
> I would also like to know if there is a way to do a SQL*Load which does
> not create ARCHIVE logs. We have one table which is truncated and fully
> reloaded on a regular basis, but we do not need to recover it in case of
> failure (becuase we can recreate it by other means). This table is
> large, and therefore creates HUGE archives, which we don't need.
> Currently we keep this table in a seperate instance with ARCHIVELOG
> disabled, but running two instances wastes memory because of the
> dedicated memory for the SGA.
>
> On Mon, 16 Feb 1998 09:22:01 -0500, Alexei Fox <alexei_fox_at_yahoo.com> wrote:
> >Hi,
> >It has recently been brought to my attention that on some DBMS (Sybase,
> >others) the operations like TRUNCATE or direct SQL*Loader load will
> >invalidate the archives generated after this operation. The reason being
> >that such operations are not logged, and therefore cannot be reproduced
> >later in case of media failure recovery. I did not find any warning in
> >Oracle manuals, and, luckily didn't have a chance to check it in real
> >life.
> >Does anyone have any comments on how Oracle handles the issue?
> >Thanks,
> >Alexei Fox
> >
>
> --
> -- Keith Moore
> President
> KMA Computer Solutions, Inc.
>
> --
> /*----C/C++--Java--VB--Pro*C--SQL--OCI--Java--Delphi--ODBC--COBOL-----*
> * When the project must be saved at all costs: *
> * KMA Computer Solutions, Inc. Project Troubleshooting/Recovery *
> *---------Linux---AIX---HPUX---SYSV---Novell---NT---OS/2---'95-------*/
Received on Tue Feb 17 1998 - 00:00:00 CST