RE: alter table move and redo log

From: Bobak, Mark <>
Date: Sun, 15 Mar 2009 03:46:31 -0400
Message-ID: <>

Note also, that since 'nologging' only applies to a small subset of operations, worrying about setting a particular object back to 'logging' is probably not very urgent or important. For example, in the case of indexes, the only thing that the object level 'nologging' setting will effect is the next rebuild, if neither 'logging' nor 'nologging' is set in the alter statement. In the case of a table, it's only insert w/ APPEND hint that would be impacted.


-----Original Message-----
From: [] On Behalf Of Kenneth Naim Sent: Sunday, March 15, 2009 2:27 AM
Subject: RE: alter table move and redo log

  1. Yes it becomes permanent as it is part of the ddl.
  2. Yes alter table logging will making it logging again.
  3. No there isn't a method within a single command to move an object nologging and have it be logging afterwards. It is very standard to rebuild certain objects nologging and then make them logging again. I do this nightly in my data warehouse where I rebuild bitmap index in parallel nologging and then alter them noparallel logging.


-----Original Message-----
From: [] On Behalf Of Yechiel Adar
Sent: Sunday, March 15, 2009 3:20 AM
Subject: Re: alter table move and redo log

If I run:
Alter table move nologging lob ...
1) Does the "nologging" part become permanent for the table or is it just for the move.
2) Will "Alter table logging" after the move command reactivate the logging of transactions for the table.
3) Is there an option to suppress login just for the move, like append does for insert?

Adar Yechiel
Rechovot, Israel

Kenneth Naim wrote:
> You can do move the table nologging and alter it logging after the move or
> do it logging and backup your archive logs to tape frequently during the
> process.



Received on Sun Mar 15 2009 - 02:46:31 CDT

Original text of this message