Managing Undo Data参考.ppt

Managing Undo Data Objectives After completing this lesson, you should be able to do the following: Describe the purpose of undo data Implement Automatic Undo Management Create and configure undo segments Obtain undo segment information from the data dictionary Managing Undo Data Overview Two methods for managing undo data exists Automatic Undo Management Manual Undo Management This lesson discusses Automatic Undo Management The term undo replaces what was known in previous versions of Oracle as rollback Undo Segment Undo Segments: Purpose Read Consistency Types of Undo Segments SYSTEM: Used for objects in the SYSTEM tablespace Non-SYSTEM: Used for objects in other tablespaces: Auto Mode: Requires an UNDO tablespace Manual Mode: Private: Acquired by a single instance Public: Acquired by any instance Deferred: Used when tablespaces are taken offline immediate, temporary, or for recovery Automatic Undo Management:Concepts Undo data is managed using an UNDO tablespace You allocate one UNDO tablespace per instance with enough space for the workload of the instance. The Oracle server automatically maintains undo data within the UNDO tablespace. Automatic Undo Management:Configuration Configure two parameters in the initialization file: UNDO_MANAGEMENT UNDO_TABLESPACE Create at least one UNDO tablespace. Automatic Undo Management:Initialization Parameters UNDO_MANAGEMENT: Specifies whether the system should use AUTO or MANUAL mode. UNDO_TABLESPACE: Specifies a particular UNDO tablespace to be used. Automatic Undo Management:UNDO Tablespace You may create the UNDO tablespace with the database by adding a clause in the CREATE DATABASE command Or create it later by using the CREATE UNDO TABLESPACE command Automatic Undo Management:Altering an UNDO Tablespace The ALTER TABLESPACE command can make changes to UNDO tablespaces. The following example adds another data file to the UNDO tablespace: Automatic Undo Management:Switching UNDO Tablespaces You may switch from u