Re: switch redo logs off for one table

igoriz_at_cmtk.net (Igor Izvekov) wrote in message news:<9f17469e.0212181423.80e6eaf_at_posting.google.com>...
> "Howard J. Rogers" <howardjr2000_at_yahoo.com.au> wrote in message news:<XL3M9.5895$jM5.16983_at_newsfeeds.bigpond.com>...
> > The answer is no.
> >
> > 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'.
> >
>
> "append" hint will also help here :
> insert /*+ append */ into BLAH select * from somewhere_else
>
> Igor Izvekov.
>

  Also, it looks like it's not possible to disable logging for bitmap indexes.
Redo is generated even if index was created with NOLOGGING and APPEND hint is used for "insert /*+ append */ into ... select ..." . According to metalink it is not documented but expected behaviour. So, if redo is not desired, bitmap indexes should be dropped first and then recreated. And even then some redo will be generated. Looks like NO LOGGING is not ZERO logging.

    Igor.

> >
> > "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 Thu Dec 19 2002 - 11:30:55 CST