Re: shutdown abort and database consistency

Actually, Mark, for those operations for which NOLOGGING is valid, all redo AND undo writing is disabled, except for any recursive data dictionary updates which will go to undo and redo, and logging of extent invalidation records in redo (I don't think they go to undo, cause I don't think they make any sense there).

In the case previously mentioned in this thread, clearly a DELETE operation will always log, so this is not a factor. However, the fact remains that NOLOGGING, when applied to an appropriate operation, will disable redo and undo.

-Mark

mark.powell_at_eds.com (Mark D Powell) wrote in message:
>
> Rick, the nologging option to my knowledge does not stop the recording
> of rollback information. The recovery of uncommited transaction data
> is still accomplished by Oracle through the reading and application of
> information stored in the rollback segments. The redo log information
> would have been read and applied during the crash recovery phase of
> startup and then rollback would be applied to rollback incomplete
> transactions. And because 8.1 and 9i open the database before
> rollback is completed sessions can encounter the situation where they
> must rollback data for incomplete transactions that occurred before
> the crash. What does v$session_wait and v$transactions show for the
> affected sessions?
>
> -- Mark D Powell --
Received on Tue Jul 09 2002 - 16:41:01 CDT