Tablespace: Locally Managed

A tablespace that manages its own extents maintains a bitmap in each datafile to keep track of the free or used status of blocks in that datafile.

Each bit in the bitmap corresponds to a block or a group of blocks. When an extent is allocated or freed for reuse, Oracle changes the bitmap values to show the new status of the blocks. These changes do not generate rollback information because they do not update tables in the data dictionary (except for special cases such as tablespace quota information).

Locally-managed tablespaces have the following advantages over dictionary-managed tablespaces:

The sizes of extents that are managed locally can be determined automatically by the system. Alternatively, all extents can have the same size in a locally-managed tablespace.

The Locally Managed feature contains the following options:

Automatic Allocation

If this box is checked, extent sizes are determined automatically by the system. The extent sizes may be variable since Oracle determines the optimal size of the extents.

Uniform

If this box is checked, you can specify an extent size or use the default size, which is 1 MB.

Size

Size of the extent to be allocated to the object.

Enter the size of the extent. Specify either kilobytes or megabytes.

Enable Logging