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 Index NOLOGGING -- was RE: ORA-1578...block corrupted...error is normal...a block...had a NOLOGGING...operation performed against

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

From: Hemant K Chitale <hkchital_at_singnet.com.sg>
Date: Wed, 24 Aug 2005 21:08:04 +0800
Message-Id: <6.2.1.2.0.20050824210534.01ff3d60@pop.singnet.com.sg>


At 08:11 AM Wednesday, Allen, Brandon wrote:
>Here is another test indicating that a direct-path insert to a nologging
>index is actually logged (like Jared has also shown), which is contrary to
>the documentation.
>
>Notice that both the table and the index are created as NOLOGGING, but the
>tablespace containing the index (TOOLS) only gets marked as unrecoverable
>at the time of the index creation (16:42) and the unrecoverable time is
>not updated after the direct-path insert, whereas the tablespace
>containing the table (SYSTEM) *does* have its unrecoverable time updated
>at the time of the direct-path insert (16:48). So, it appears the table
>changes are not logged, and therefore are unrecoverable as would be
>expected, but the index changes *are* still logged and therefore the index
>is recoverable, contrary to the documentation:

Yes, of course. Even if you marked the Index NOLOGGING the Index Updates were NOT bulk updates -- to the
Index they are regular DML. They will be LOGged. {The Index Create was a NOLOGging operation, correctly}

Hemant K Chitale
http://web.singnet.com.sg/~hkchital

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Aug 24 2005 - 08:10:20 CDT

Original text of this message

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