Re: ORA-1578...block corrupted...error is normal...a block...had a NOLOGGING...operation performed against
- From: "Radoulov, Dimitre" <cichomitiko@xxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 23 Aug 2005 23:32:06 +0200
A little wrap up:
"Only the following operations support the NOLOGGING mode:
DML: direct-load INSERT (serial or parallel), Direct Loader (SQL*Loader)
DDL: CREATE TABLE ... AS SELECT, CREATE INDEX, ALTER INDEX ... REBUILD, ALTER
INDEX ... REBUILD PARTITION, ALTER INDEX ... SPLIT PARTITION, ALTER TABLE ...
SPLIT PARTITION, and ALTER TABLE ... MOVE PARTITION
In NOLOGGING mode, data is modified with minimal logging (to mark new extents
INVALID and to record dictionary changes). When applied during media recovery,
the extent invalidation records mark a range of blocks as logically corrupt,
because the redo data is not logged. Therefore, if you cannot afford to lose
the object, you should take a backup after the NOLOGGING operation."
Table Mode Insert Mode ArchiveLog mode result
----------- ------------- ----------------- ----------
LOGGING APPEND ARCHIVE LOG redo generated
NOLOGGING APPEND ARCHIVE LOG no redo
LOGGING no append "" redo generated
NOLOGGING no append "" redo generated
LOGGING APPEND noarchive log mode no redo
NOLOGGING APPEND noarchive log mode no redo
LOGGING no append noarchive log mode redo generated
NOLOGGING no append noarchive log mode redo generated
Regards
Dimitre Radoulov
Other related posts:
