***Checked for relevance on 25-Jul-2010***

goal: How to Avoid Generation of Redolog Entries
fact: Oracle Server - Enterprise Edition 8.1
fact: Oracle Server - Enterprise Edition 9.0.1
fact: Oracle Server - Enterprise Edition 9.2
fact: Oracle Server - Enterprise Edition 10.1
fact: Oracle Server - Enterprise Edition 10.2
fact: Oracle Server - Enterprise Edition 11.1
fact: Oracle Server - Enterprise Edition 11.2

fix:

The option NOLOGGING valid since Oracle8 can be used to avoid
the redolog entries generation for a certain operation,
that can be easily recovered without using the database
recovery mechanism.

The following operations can make use of nologging mode:

- direct load (SQL*Loader)
- direct-load INSERT
- CREATE TABLE ... AS SELECT
- CREATE INDEX
- ALTER TABLE ... MOVE PARTITION
- ALTER TABLE ... SPLIT PARTITION
- ALTER INDEX ... SPLIT PARTITION
- ALTER INDEX ... REBUILD
- ALTER INDEX ... REBUILD PARTITION
- INSERT /*+APPEND*/ INTO AS SELECT ...
- INSERT, UPDATE, and DELETE on LOBs in
      NOCACHE NOLOGGING mode stored out of line

References:
    Oracle8i Concepts Manual
    Oracle8i SQL Reference
    Oracle9i Concepts Manual
    Oracle9i SQL Reference

Current version:
   Oracle® Database SQL Language Reference
   11g Release 2 (11.2)

References

http://docs.oracle.com/cd/E11882_01/server.112/e26088/clauses005.htm#SQLRF30009

ITPub博客

How to Avoid Generation of Redolog Entries (Doc ID 188691.1)

References

最新文章