dbf
16 /u08/oradata/ord/idx07.dbf
17 /u08/oradata/ord/idx08.dbf
17 rows selected.
Other than file numbers 8 and 9, all the datafiles in the ord database are OFA compliant and
are spread out over four different mount points. The tablespace name in file number 8 is too long,
and file number 9 does not have a numeric two-digit counter to represent new datafiles for the
same tablespace.
File Type Filename Format Variables
Control files control.ctl None.
Redo log files redo
.log n is a two-digit number.
Datafiles .dbf t is an Oracle tablespace name, and n is a
two-digit number.
TABLE 3-1 OFA-Compliant Control File, Redo Log File, and Datafile Naming Conventions
Chapter 3: Planning and Managing Tablespaces 71
ASM Environment
In an ASM environment, the executables are stored in the directory structure presented previously;
however, if you browsed the directory /u02/oradata in Figure 3-5, you would see no files. All the
control files, redo log files, and datafiles for the instance dw are managed by the ASM instance
+ASM on this server.
The actual datafile names are not needed for most administrative functions because ASM files are
all Oracle Managed Files (OMF). This eases the overall administrative effort required for the database.
Within the ASM storage structure, an OFA-like syntax is used to subdivide the file types even further:
SQL> select file#, name from v$datafile;
FILE# NAME
---------- ----------------------------------------
1 +DATA/dw/datafile/system.
Pages:
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170