dbf' size 1g
default temporary tablespace temp01
tempfile '/u03/oradata/ord/temp001.dbf' size 150m
undo tablespace undotbs01
datafile '/u01/oradata/ord/undo001.dbf' size 500m;
If the undo tablespace cannot be successfully created in the create database command, the
entire operation fails. The error must be corrected, any files remaining from the operation must
be deleted, and the command must be reissued.
Although the undo tablespace clause in the create database command is optional, if it is
omitted and Automatic Undo Management is enabled, an undo tablespace is still created with
an autoextensible datafile with an initial size of 10MB and the default name SYS_UNDOTBS.
Creating an Undo Tablespace with CREATE TABLESPACE
Any time after the database is created, a new undo tablespace can be created. An undo
tablespace is created just as any other tablespace with the addition of the undo keyword:
create undo tablespace undotbs02
datafile '/u01/oracle/rbdb1/undo0201.dbf'
size 500m reuse autoextend on;
Depending on the volatility of the database or the expectation that the undo needs of the database
may increase dramatically in the future, we start out this tablespace at only 500MB and allow it
to grow.
Extents in an undo tablespace must be system managed; in other words, you can only specify
extent management as local autoallocate.
Creating an Undo Tablespace Using EM Database Control
Creating an undo tablespace is straightforward using Enterprise Manager Database Control.
Pages:
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369