Re: Change index from nologging to logging
Date: Tue, 24 Mar 2009 15:05:44 -0700 (PDT)
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?
- 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...
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.
Hemant K ChitaleReceived on Tue Mar 24 2009 - 17:05:44 CDT