RE: Change index from nologging to logging

From: FmHabash <fmhabash_at_gmail.com>
Date: Sun, 12 Apr 2009 18:06:56 -0400
Message-ID: <49e26601.0913c00a.4f7e.72e0_at_mx.google.com>

We manage this situation by a combination of any of the following measures.. 1- force logging db-wide. With DG, this is the safest way. 2- monitor for nologging activity and alert at priority one.

Thank you.

-----Original Message-----
From: Powell, Mark D <mark.powell_at_eds.com> Sent: Wednesday, March 25, 2009 8:04 AM
To: oracle-l_at_freelists.org
Subject: RE: Change index from nologging to logging  

Yes, it is wrong. The manuals are often technically wrong and sometimes like this one the manuals are just out and out wrong based on the wording.

• Mark D Powell -- Phone (313) 592-5148

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Charlotte Hammond Sent: Tuesday, March 24, 2009 6:06 PM
To: hkchital_at_singnet.com.sg; oracle-l_at_freelists.org Subject: Re: Change index from nologging to logging

Hi Hemant,

Thanks for your reply. That seems clear: so the line in the manual stating that "This setting also determines whether subsequent Direct Loader (SQL*Loader) and direct-path INSERT operations against the index are logged or not logged." is just wrong?

Thanks
Charlotte

• Original Message ---- From: Hemant K Chitale <hkchital_at_singnet.com.sg> To: Charlotte Hammond <charlottejanehammond_at_yahoo.com>; oracle-l_at_freelists.org Sent: Tuesday, March 24, 2009 4:15:43 PM Subject: Re: Change index from nologging to logging

At 05:02 AM Tuesday, Charlotte Hammond wrote: <sorry, the text of your email has been snipped by the spam filter, I got only your email header !, but retrieving your email from the oracle-l archives>

In the manual (SQL Reference 10g) it says:

Specify whether the creation of the
index will be logged (LOGGING) or not logged (NOLOGGING) in the redo log file.
This setting also determines whether subsequent Direct Loader (SQL*Loader) and direct-path INSERT operations against the index are logged or not logged.
LOGGING is the default.Are you not counting direct load/insert as DML, or do you believe this statement is wrong? I'd like to test it but so busy just now...

See
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:5280 714813869
"

Followup August 29, 2008 - 11pm US/Eastern: indexes always, always, always generate redo during any insert, any - any - any insert.

We were talking only about tables.

insert /*+ append */ - since it is done in bulk will MINIZE the redo, but it'll generate redo for the indexes *always* if the index is maintained.
"

Also see
http://hemantoracledba.blogspot.com/2008/05/append-nologging-and-indexes .html

and
http://www.freelists.org/post/oracle-l/Question-about-Append-hint-in-Ins ert,4

Hemant K Chitale

http://hemantoracledba.blogspot.com       

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


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



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

Received on Sun Apr 12 2009 - 17:06:56 CDT