Space Management in Tablespaces
Posted by thakuranupam on November 8, 2009
Locally Managed Tablespaces
- Free Extent Information is NOT stored in Data Dictionary
- Bitmap Segments are used to keep track of the free space usage
- Within the tablespace, there are bitmap segments
- Each bit in the Bitmap corresponds to a Data Block or a group of Data Blocks and the value in the bit indicates that the blocks are free or used
- Whenever a block is used or freed for reuse, Oracle changes the value of the bitmap to show the new status of the block
- Contention is significantly reduced on the data dictionary tables
- Coalescing of free space is NOT required
Dictionary Managed Tablespaces
- This is the default method for the creation of tablespace
- Free Extent Information is stored in Data Dictionary
- Contention is significantly INCREASED on the data dictionary tables
- Oracle updates the appropriate tables in the data dictionary whenever an extent is allocated or deallocated in relation to the tablespace
- Coalescing is required in frequently updated segments in Dictionary Managed Tablespaces
To indicate the Space Management during the creation of a Tablespace, EXTENT MANAGEMENT clause needs to be specified as follows:
EXTENT_MANAGEMENT [DICTIONARY | LOCAL [AUTOALLOCATE | UNIFORM [SIZE integer [K|M]]]
Advertisement