Veritas File System 5.1 SP1 Administrator"s Guide (5900-1499, April 2011)

DB_CREATE_FILE_DEST = '/PROD'
DB_CREATE_ONLINE_LOG_DEST_1 = '/PROD'
db_block_size = 4096
db_name = PROD
$ sqlplus /nolog
SQL> connect / as sysdba
SQL> startup nomount pfile= initPROD.ora
The Oracle instance starts.
Total System Global Area 93094616 bytes
Fixed Size 279256 bytes
Variable Size 41943040 bytes
Database Buffers 50331648 bytes
Redo Buffers 540672 bytes
To implement a layout that places files associated with the EMP_TABLE tablespace
in a directory separate from the EMP_INDEX tablespace, use the ALTER SYSTEM
statement. This example shows how OMF handles file names and storage clauses
and paths. The layout allows you to think of the tablespaces as objects in a file
system as opposed to a collection of datafiles. Since OMF uses the Oracle Disk
Manager file resize function, the tablespace files are initially created with the
default size of 100 MB and ODM increases the size as needed. Use the MAXSIZE
attribute to limit growth.
The following example shows the commands for creating an OMF database and
for creating the EMP_TABLE and EMP_INDEX tablespaces in their own locale:
SQL> create database PROD;
Note: The directory must exist for OMF to work, so the SQL*Plus HOST command
is used to create the directories:
The database is created.
SQL> HOST mkdir /PROD/EMP_TABLE;
SQL> ALTER SYSTEM SET DB_CREATE_FILE_DEST = '/PROD/EMP_TABLE';
The system is altered.
SQL> create tablespace EMP_TABLE DATAFILE AUTOEXTEND ON MAXSIZE \
500M;
A tablespace is created.
Using Veritas Extension for Oracle Disk Manager
About Oracle Disk Manager and Oracle Managed Files
110