Re: Question on LOGGING which not getting enabled permanently

From: Gaja Krishna Vaidyanatha <gajav_at_yahoo.com>
Date: Mon, 21 Jan 2013 09:31:41 -0800 (PST)
Message-ID: <1358789501.55089.YahooMailNeo_at_web180903.mail.ne1.yahoo.com>

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 :)

Cheers,

Gaja
 
Gaja Krishna Vaidyanatha,
CEO & Founder, DBPerfMan LLC
http://www.dbperfman.com
http://www.dbcloudman.com

Phone - +1-650-743-6060
LinkedIn - http://www.linkedin.com/in/gajakrishnavaidyanatha

Co-author: Oracle Insights:Tales of the Oak Table - http://www.apress.com/9781590593875 Primary Author: Oracle Performance Tuning 101 - http://www.amzn.com/0072131454 Enabling Cloud Deployment & Management for Oracle & Big Data

---

 From: Sriram Kumar <k.sriramkumar_at_gmail.com> To: dbaorapps_at_gmail.com
Cc: oracle-l_at_freelists.org; ora-apps-dba_at_freelists.org Sent: Monday, January 21, 2013 3:32 AM
Subject: Re: Question on LOGGING which not getting enabled permanently  

Hi,
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 <dbaorapps_at_gmail.com> 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
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

--
http://www.freelists.org/webpage/oracle-l

--
http://www.freelists.org/webpage/oracle-l

Received on Mon Jan 21 2013 - 18:31:41 CET