On many
occasions, a DBA would drop a tablespace, but would forget to delete the underlying datafiles,
thus wasting space and the time it took to back up files that were no longer used by the database.
Using OMF, Oracle not only automatically creates and deletes the files in the specified
directory location, it ensures that each filename is unique. This avoids corruption and database
downtime in a non-OMF environment due to existing files being overwritten by a DBA inadvertently
creating a new datafile with the same name as an existing datafile, and using the REUSE clause.
In a test or development environment, OMF reduces the amount of time the DBA must spend
on file management and lets him or her focus on the applications and other aspects of the test
?–
?–
?–
?–
?–
?–
178 Oracle Database 11g DBA Handbook
database. OMF has an added benefit for packaged Oracle applications that need to create
tablespaces: The scripts that create the new tablespaces do not need any modification to include
a datafile name, thus increasing the likelihood of a successful application deployment.
Migrating to OMF from a non-OMF environment is easy, and it can be accomplished over a
longer time period. Non-OMF files and OMF files can coexist indefinitely in the same database.
When the appropriate initialization parameters are set, all new datafiles, control files, and redo
log files can be created as OMF files, while the previously existing files can continue to be managed
manually until they are converted to OMF, if ever.
Pages:
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325