Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

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 100MB and grow 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.
Note: The directory must exist for OMF to work, so the SQL*Plus HOST command
is used to create the directories:
SQL> create database PROD;
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.
SQL> ALTER SYSTEM SET DB_CREATE_FILE_DEST = '/PROD/EMP_INDEX';
The system is altered.
SQL> create tablespace EMP_INDEX DATAFILE AUTOEXTEND ON MAXSIZE \
100M;
A tablespace is created.
Use the ls command to show the newly created database:
$ ls -lFR
total 638062
drwxr-xr-x 2 oracle9i dba 96 May 3 15:43 EMP_INDEX/
drwxr-xr-x 2 oracle9i dba 96 May 3 15:43 EMP_TABLE/
-rw-r--r-- 1 oracle9i dba 104858112 May 3 17:28 ora_1_BEhYgc0m.log
-rw-r--r-- 1 oracle9i dba 104858112 May 3 17:27 ora_2_BEhYu4NA.log
Using Veritas Extension for Oracle Disk Manager
About Oracle Disk Manager and Oracle Managed Files
124