Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: ORA-1578...block corrupted...error is normal...a block...had a NOLOGGING...operation performed against

RE: ORA-1578...block corrupted...error is normal...a block...had a NOLOGGING...operation performed against

From: <oracle-l-bounce_at_freelists.org>
Date: Wed, 24 Aug 2005 17:01:17 -0700
Message-ID: <04DDF147ED3A0D42B48A48A18D574C45023614B2@NT15.oneneck.corp>


Here is Tom Kyte's response: "the documentation is in error, thanks-- one more to file when I get back :)"

So, I guess that's settle then. Whew! :-)

-----Original Message-----
From: Allen, Brandon
Sent: Wednesday, August 24, 2005 10:00 AM To: 'Mladen Gogala'
Cc: oracle-l
Subject: RE: ORA-1578...block corrupted...error is normal...a block...had a NOLOGGING...operation performed against

Actually, the documentation does give *some* indication that the index maintenance portion is not "direct", although it's not very clear, and then clouded even further by the wording in the logging_clause section mentioned earlier:

(From http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96524/c21dlins.htm#10696)

Index Maintenance with Direct-Path INSERT

Oracle performs index maintenance at the end of direct-path INSERT operations on tables (partitioned or nonpartitioned) that have indexes. This index maintenance is performed by the parallel execution servers for parallel direct-path INSERT or by the single process for serial direct-path INSERT. You can avoid the performance impact of index maintenance by dropping the index before the INSERT operation and then rebuilding it afterward.

I also found a thread on this same topic over at asktom.oracle.com (http://asktom.oracle.com/pls/ask/f?p=4950:8:16044210042548460889:::::) , and here is what Tom says:

"you have indexes on the table. indexes cannot be "appended" to, they must be modified. These modifications must be logged. The redo/undo for the table itself is not generated, the redo/undo for the INDEXES always is."

So, I've posted a note to the same thread asking Tom to confirm if there is a documenation bug.

Regards,
Brandon

-----Original Message-----
From: Mladen Gogala [mailto:gogala_at_sbcglobal.net] Sent: Wednesday, August 24, 2005 9:30 AM To: Allen, Brandon
Cc: oracle-l
Subject: Re: ORA-1578...block corrupted...error is normal...a block...had a NOLOGGING...operation performed against

On 08/24/2005 12:24:28 PM, Allen, Brandon wrote:
> Mladen, you also seem to be missing the point. You say the documentation is wrong - but then you go on to agree with it later in the same paragraph ("Oracle, as a matter of fact, allows you to bypass logging for speed").
>

Documentation is wrong when it mentions "direct inserts into index". There is no such thing.

-- 
Mladen Gogala
http://www.mgogala.com



Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Aug 24 2005 - 19:01:52 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US