Temporary Tablespace Groups
-
Multiple temporary tablespaces can be used
in different sessions at the same time. Slave processes in a
single parallel operation can use multiple temporary
tablespaces. Multiple default temporary tablespaces can be
specified at the database level.
-
More than one default temporary tablespace can be defined for a database. A single database
operation can use multiple temporary tablespaces in sorting
operations. This prevents large tablespace operations from
running out of space. If a TTG is specified as the default
temporary tablespace for the database, no tablespaces in that
group can be dropped.
In Oracle Database 10g, the DBA can simply
rename any tablespace excluding the SYSTEM or SYSAUX
tablespaces. This helps in situations like transporting a
tablespace to a target database which has a similar tablespace
with the same name.
Each database user has a permanent
tablespace for storing permanent data and a temporary tablespace
for storing temporary data. In previous versions of Oracle, if a
user is created without specifying a default tablespace, SYSTEM
tablespace will be allotted as default. For 10g, a default
permanent tablespace can be defined to be used for all new users
without a specific permanent tablespace.
By creating a default permanent tablespace,
non-system user objects can be prevented from being created in
the SYSTEM tablespace.
BigFile Tablespaces (BFT)
A BFT is a tablespace containing a single
very large data file. With the new addressing scheme in 10g, up
to four billion blocks are
permitted in a single data file and file sizes can be from 8
Tera Bytes to 128 Tera Bytes.
To distinguish a regular tablespace from BFT, a regular
tablespace is called a small file tablespace. Oracle Database
10g can be a mixture of small file tablespaces and bigfile
tablespaces.
