This location is used for redo log files and control
files if DB_CREATE_ONLINE_LOG_DEST_n is not
specified.
DB_CREATE_ONLINE_LOG_DEST_n Specifies the default location to store redo log files
and control files when no pathname is specified for
redo log files or control files at database-creation
time. Up to five destinations can be specified with
this parameter, allowing up to five multiplexed
control files and five members of each redo log group.
DB_RECOVERY_FILE_DEST Defines the default pathname in the server??™s file
system where RMAN backups, archived redo logs,
and flashback logs are located. Also used for redo
log files and control files if neither DB_CREATE_
FILE_DEST nor DB_CREATE_ONLINE_LOG_DEST_n
is specified.
TABLE 6-1 OMF-Related Initialization Parameters
Chapter 6: Monitoring Space Usage 179
backup of a bigfile tablespace uses a single process; a number of smaller tablespaces, however,
can be backed up using parallel processes and will most likely take less time to back up than a
single bigfile tablespace.
Creating a bigfile tablespace is as easy as adding the bigfile keyword to the create tablespace
command:
SQL> create bigfile tablespace whs01
2 datafile '/u06/oradata/whs01.dbf' size 10g;
Tablespace created.
If you are using OMF, then the datafile clause can be omitted. To resize a bigfile tablespace,
you can use the resize clause:
SQL> alter tablespace whs01 resize 80g;
Tablespace altered.
Pages:
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327