RE: Question on LOGGING which not getting enabled permanently

From: Ric Van Dyke <>
Date: Mon, 21 Jan 2013 12:19:38 -0600
Message-ID: <>

I'm pretty sure that INITRANS is still used, MAXTRANS is effectively ignored.

11.2 SQL Reference:
Existing objects for which a value of MAXTRANS has already been set retain that setting. However, if you attempt to change the value for MAXTRANS, Oracle ignores the new specification and substitutes the value 255 without returning an error.

  • Ric

-----Original Message-----
From: [] On Behalf Of Gaja Krishna Vaidyanatha Sent: Monday, January 21, 2013 12:32 PM
To:; Cc:; Subject: Re: Question on LOGGING which not getting enabled permanently

Hi Shiva,
As an aside from your real question on the LOGGING issue, may I ask the specific reason for configuring INITRANS? I know what INITRANS is for, so that is not my question. But with Automatic Segment Space Management in Oracle 9i and up, Oracle should be (in theory) automatically managing the number of ITL slots in the block. In fact, I think the docs state that any configuration of INITRANS will be ignored. Are you not using ASSM for the tablespaces in question? Or have you had issues with ITL waits even with ASSM configured in the tablespaces? Just curious :)


Gaja Krishna Vaidyanatha,
CEO & Founder, DBPerfMan LLC

Phone - +1-650-743-6060
LinkedIn -

Co-author: Oracle Insights:Tales of the Oak Table - Primary Author: Oracle Performance Tuning 101 - Enabling Cloud Deployment & Management for Oracle & Big Data

 From: Sriram Kumar <> To:
Cc:; Sent: Monday, January 21, 2013 3:32 AM
Subject: Re: Question on LOGGING which not getting enabled permanently  

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 - 19:19:38 CET

Original text of this message