RE: Question on LOGGING which not getting enabled permanently
- From: "Don Granaman" <granaman@xxxxxxx>
- To: <gajav@xxxxxxxxx>, "'Ric Van Dyke'" <ric.van.dyke@xxxxxxxxxx>, <k.sriramkumar@xxxxxxxxx>, <dbaorapps@xxxxxxxxx>
- Date: Tue, 22 Jan 2013 02:12:59 -0600
Me too, but older...
Don Granaman - OraSaurus
Honk if you remember UFI !
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Gaja Krishna Vaidyanatha
Sent: Monday, January 21, 2013 1:59 PM
To: Ric Van Dyke; k.sriramkumar@xxxxxxxxx; dbaorapps@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx; ora-apps-dba@xxxxxxxxxxxxx
Subject: Re: Question on LOGGING which not getting enabled permanently
Hey Ric,
Thanks for the doc snippet, but I could have sworn that I read somewhere
that INITRANS was also automatically handled. May be I am getting old :)
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: Ric Van Dyke <ric.van.dyke@xxxxxxxxxx>
To: gajav@xxxxxxxxx; k.sriramkumar@xxxxxxxxx; dbaorapps@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx; ora-apps-dba@xxxxxxxxxxxxx
Sent: Monday, January 21, 2013 10:19 AM
Subject: RE: Question on LOGGING which not getting enabled permanently
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: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Gaja Krishna Vaidyanatha
Sent: Monday, January 21, 2013 12:32 PM
To: k.sriramkumar@xxxxxxxxx; dbaorapps@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx; ora-apps-dba@xxxxxxxxxxxxx
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 :)
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@xxxxxxxxx>
To: dbaorapps@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx; ora-apps-dba@xxxxxxxxxxxxx
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@xxxxxxxxx> 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
>
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
