Storage Structure and Relationships教学文稿.ppt

Automatic Undo Management: Initialization Parameters UNDO_MANAGEMENT The UNDO_MANAGEMENT parameter determines the undo mode of the database. The parameter can be set to one of two values, AUTO or MANUAL, and must be set in the initialization file. UNDO_MANAGEMENT cannot be changed dynamically after the database starts. AUTO mode sets the database to automatic undo management and requires an UNDO tablespace. In MANUAL mode, the default value, you can create and manage undo segments when needed within the database as in previous versions of the Oracle server. UNDO_TABLESPACE Specifies the UNDO tablespace to be used. This parameter can be set in the initialization files or altered dynamically using the ALTER SYSTEM command. ALTER SYSTEM SET undo_tablespace = UNDOTBS; Automatic Undo Management Configuration Automatic undo management requires an UNDO tablespace. More than one UNDO tablespace may exist in the database, but only one UNDO tablespace can be active. You can create the UNDO tablespace with the database by adding a clause to the CREATE DATABASE statement. During database creation, if the UNDO_MANAGEMENT parameter is set to AUTO and you omit the UNDO tablespace clause from the CREATE DATABASE statement then the Oracle server creates an UNDO tablespace with the name SYS_UNDOTBS. The default data file, for data file tablespace SYS_UNDOTS, will have the name dbu1oracle_sid.dbf located in $ORACLE_HOME/dbs, the size is operating system dependent, and AUTOEXTEND is ON. After database creation, you can create an UNDO tablespace using the CREATE UNDO TABLESPACE command. Types of Segments LOB Segment One or more columns in a table can be used to store large objects (LOBs) such as text documents, images, or videos. If the column is large, the Oracle server stores these values in separate segments known as LOB segments. The table contains only a locator or a pointer to the location of the corresponding LOB data. Nested Table A column in a table may be made up of a user-de