A tablespace is a logical storage unit - multiple application objects (e.g. tables) can be stored in one tablespace. A database can contain multiple tablespaces.
A tablespace can be online or offline (not accessible), and can contain one or more datafiles, each of which can be online or offline.
There is no relationship between a tablespace and a schema.
Objects in the same schema can be in different tablespaces, and a tablespace can hold objects from different schemas.
A tablespace can be set to read-only to eliminate the need to perform backup and recovery of large, static portions of the database.
A tablespace can be set to temporary to optimise the storage of temporary objects.
Tablespaces can use one of two methods to keep track of free and used space: Dictionary-managed or Locally managed - this is chosen when the tablespace is created and cannot be altered at a later date.
When creating an LMT, the storage parameters NEXT, PCTINCREASE, MINEXTENTS, MAXEXTENTS, and DEFAULT STORAGE are not required (invalid syntax).
An LMT can have either uniform or variable extent sizes. Variable extents are determined automatically by the system. When you create the tablespace, the UNIFORM or AUTOALLOCATE (system-managed) clause specifies the type of allocation.
- For uniform extents, you can specify an extent size or use the default size, which is 1 MB. Temporary tablespaces that manage their extents locally can only use this type of allocation.
- For system-managed extents, you can specify the size of the initial extent and Oracle determines the optimal size of additional extents, with a minimum extent size of 64 KB. This is the default for permanent tablespaces.
When you create a locally managed tablespace using the CREATE TABLESPACE statement, the SEGMENT SPACE MANAGEMENT clause lets you specify how free and used space within a segment is to be managed:
SEGMENT SPACE MANAGEMENT MANUAL - Use free lists for managing free space within segments. Free lists are lists of data blocks that have space available for inserting rows. (This is the default.)
SEGMENT SPACE MANAGEMENT AUTO - Use bitmaps to automatically manage the free space within segments.
CREATE TABLESPACE mytbs1
DATAFILE '/u01/oracle/data/mytbs01.dbf' SIZE 500M
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
Locally managed temporary tablespaces have temporary datafiles (tempfiles), which are similar to ordinary datafiles except that:
- You cannot create a tempfile with the ALTER DATABASE statement.
- You cannot rename a tempfile or set it to read-only.
- Tempfiles are always set to NOLOGGING mode.
- When you create or resize tempfiles, they are not always guaranteed allocation of disk space for the file size specified. On certain file systems (for example, UNIX) disk blocks are allocated not at file creation or resizing, but before the blocks are accessed.
- Tempfile information is shown in the dictionary view DBA_TEMP_FILES and the dynamic performance view V$TEMPFILE, but not in DBA_DATA_FILES or the V$DATAFILE view.
Note: this arrangement enables fast tempfile creation and resizing; however, the disk could run of space later when the tempfiles are accessed.
A tablespace that uses the data dictionary to manage its extents has incremental extent sizes, which are determined by the storage parameters INITIAL, NEXT, and PCTINCREASE. These can be adjusted to control the extent sizes. When additional space is needed, the NEXT and PCTINCREASE parameters determine the sizes of new extents.
Every Oracle database contains a tablespace named SYSTEM, which Oracle creates automatically when the database is created.
The SYSTEM tablespace always contains the data dictionary tables for the entire database.
All data stored on behalf of stored PL/SQL program units (procedures, functions, packages, and triggers) resides in the SYSTEM tablespace.
The SYSTEM tablespace is always online when the database is open.
A temporary tablespace is optimised for the storage of temporary data (such as sorting the results of a query.)
You specify a default temporary tablespace when you create a database, using the DEFAULT TEMPORARY TABLESPACE extension to the CREATE DATABASE statement.
You can drop the default temporary tablespace. If you do, the SYSTEM tablespace will be used as default temporary tablespace. However, in future releases, this might not be allowed. You cannot make the default temporary tablespace permanent or take it offline.
To change a user account to use a non-default temp tablespace
ALTER USER <user_account> SET TEMPORARY TABLESPACE <temp_tbsp>
Moving data by transporting tablespaces can be orders of magnitude faster than either export/import or unload/load of the same data, because transporting a tablespace involves only copying datafiles and integrating the tablespace metadata.
You can move a tablespace from one Oracle database to another (without copying or moving any files) or you can clone (copy) the tablespace.
Transporting tablespaces will only work between databases on the same platform.
When you transport tablespaces you can also move index data, so you do not have to rebuild the indexes after importing or loading the table data.
"…This sense of order is what makes freedom possible. There are 11 political parties in Denmark because there is only one way to eat lunch. You don't eat at your desk or as you drive and you don't walk down the street munching a hot dog. You eat at a table with a napkin and a knife and fork and candle" ~ Garrison Keillor
© Copyright SS64.com 1999-2013
Some rights reserved