Re: Question on LOGGING which not getting enabled permanently

From: Sriram Kumar <>
Date: Mon, 21 Jan 2013 17:02:33 +0530
Message-ID: <>

Tablespace logging level takes precedence if no explicit option is provided. check the tablespace level settings for the new partitions and do an alter tablespace logging to change that behaviour

best regards

sriram kumar

On Mon, Jan 21, 2013 at 4:31 PM, Apps DBA <> wrote:

> Hi Gurus,
> We have a scenario in the database related to LOGGING. We enabled LOGGING
> option for a table and had altered the INITRANS option from 2 to 11 and 10
> for
> Table and Indexes respectively. What we found that for all the existing
> partitions and indexes, the LOGGING got enabled but for any new partitions
> NOLOGGING still coming out to be.
> If NOLOGGING continue to remain, then it may impact the DB backup as well
> as future recoveries. Has anyone come across this or what other changes
> have to be done? Please advice.
> Thanks,
> A.Shiva
> --

Received on Mon Jan 21 2013 - 12:32:33 CET

Original text of this message