Migrating a dictionary-managed tablespace to a locally managed tablespace is very
straightforward using the DBMS_SPACE_ADMIN built-in package:
execute sys.dbms_space_admin.tablespace_migrate_to_local('USERS')
After upgrading a database to either Oracle9i, Oracle 10g, or Oracle 11g, you may also want to
consider migrating the SYSTEM tablespace to an LMT; if so, a number of prerequisites are in order:
Before starting the migration, shut down the database and perform a cold backup of the
database.
Any non-SYSTEM tablespaces that are to remain read/write should be converted to LMTs.
The default temporary tablespace must not be SYSTEM.
If automatic undo management is being used, the undo tablespace must be online.
For the duration of the conversion, all tablespaces except for the undo tablespace must
be set to read-only.
The database must be started in RESTRICTED mode for the duration of the conversion.
If any of these conditions are not met, the TABLESPACE_MIGRATE_TO_LOCAL procedure will
not perform the migration.
Using OMF to Manage Space
In a nutshell, Oracle-Managed Files (OMF) simplifies the administration of an Oracle database. At
database-creation time, or later by changing a couple parameters in the initialization parameter
file, the DBA can specify a number of default locations for database objects such as datafiles,
redo log files, and control files. Prior to Oracle9i, the DBA had to remember where the existing
datafiles were stored by querying the DBA_DATA_FILES and DBA_TEMP_FILES views.
Pages:
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324