Database Reference
In-Depth Information
When you rename a tablespace, Oracle updates the name of the tablespace in the data dictionary, control files,
and data file headers. Keep in mind that renaming a tablespace doesn't rename any associated data files. See the
section “Renaming or Relocating a Data File,” later in this chapter, for information on renaming data files.
■
Note
you can't rename the
SYSTEM
tablespace or the
SYSAUX
tablespace.
Controlling the Generation of Redo
For some types of applications, you may know beforehand that you can easily re-create the data. An example might
be a data warehouse environment in which you perform direct path inserts or use SQL*Loader to load data. In these
scenarios you can turn off the generation of redo for direct path loading. You use the
NOLOGGING
clause to do this:
create tablespace inv_mgmt_data
datafile '/u01/dbfile/O12C/inv_mgmt_data01.dbf' size 100m
segment space management auto
nologging;
If you have an existing tablespace and want to alter its logging mode, use the
ALTER TABLESPACE
statement:
SQL> alter tablespace inv_mgmt_data nologging;
You can confirm the tablespace logging mode by querying the
DBA_TABLESPACES
view:
SQL> select tablespace_name, logging from dba_tablespaces;
The generation of redo logging can't be suppressed for regular
INSERT
,
UPDATE
, and
DELETE
statements. For
regular data manipulation language (DML) statements, the
NOLOGGING
clause is ignored. The
NOLOGGING
clause does
apply, however, to the following types of DML:
INSERT
statements
•
Direct path
•
The
NOLOGGING
clause also applies to the following types of DDL statements:
Direct path SQL*Loader
CREATE TABLE ... AS SELECT
(
NOLOGGING
only affects the initial create, not subsequent
regular DML, statements against the table)
•
ALTER TABLE ... MOVE
•
ALTER TABLE ... ADD/MERGE/SPLIT/MOVE/MODIFY PARTITION
•
CREATE INDEX
•
ALTER INDEX ... REBUILD
•
CREATE MATERIALIZED VIEW
•
ALTER MATERIALIZED VIEW ... MOVE
•
CREATE MATERIALIZED VIEW LOG
•
ALTER MATERIALIZED VIEW LOG ... MOVE
•
