Datasheet

Using ASM Storage 35
default ASM destinations be defining incomplete ASM filenames. The following database
parameters take incomplete ASM filenames:
DB_CREATE_FILE_DEST

DB_CREATE_ONLINE_LOG_DEST_n

DB_RECOVERY_FILE_DEST

CONTROL_FILES

LOG_ARCHIVE_DEST_n

(log_archive_dest_format will be ignored)
LOG_ARCHIVE_DEST

(log_archive_dest_format will be ignored)
STANDBY_ARCHIVE_DEST

Here is an example of using an incomplete name when setting the DB_CREATE_FILE_DEST
parameter so that it will use the ASM disk group
+sp_dgroup1:
alter system set db_create_file_dest=’+cooked_dgroup1’ scope=both;
Creating a Tablespace Using an ASM Disk Group
as the Destination
There are different ways to create tablespaces using ASM disks. In this section, we will first
look at creating an ASM tablespace, allowing the default ASM disk location to be used (as
a result of having set the
DB_CREATE_FILE_DEST parameter as we did earlier). We will then
look at how to create a tablespace datafile by explicitly referencing the ASM disk group
that it is supposed to be assigned to.
Creating Tablespaces Using Default ASM Assignments
Now that you have seen how to define a default ASM location, you can use the create
tablespace
command to create a tablespace that will have a file in the ASM disk group by
default, as shown in this example:
create tablespace test_rgf datafile size 100k;
Let’s see where Oracle put the datafile now by querying the DBA_DATA_FILES view:
Select tablespace_name, file_name
from dba_data_files Where tablespace_name=’TEST_RGF’;
TABLESPACE FILE_NAME
---------- ---------------------------------------------------------
TEST_RGF +COOKED_DGROUP1/11gDB/datafile/test_rgf.256.613064385
95134c01.indd 35 1/28/09 9:43:45 AM