7 Administering Oracle ASM Files, Directories, and Templates

Single File Creation Form

A single file creation form is used to create a single file, such as a data file or a control file. The form of the Oracle ASM filename in this type is either an alias, such as +data/orcl/ctl.f, or an incomplete file name, such as a disk group name preceded by a plus sign (+data). You use the alias or disk group name where a filename is called for in an SQL statement, such as CREATE TABLESPACE, CREATE CONTROLFILE.

Multiple File Creation Form

A multiple file creation form is used multiple times to create Oracle ASM files, such as when assigning a value to the initialization parameter DB_CREATE_FILE_DEST. You can also issue a CREATE TABLESPACE statement (without a filename specification) multiple times. Each time, Oracle ASM creates a different unique data file name.

When using the multiple file creation form, you can use an incomplete filename form, such as a disk group name preceded by a plus sign (+data). In this case, you set DB_CREATE_FILE_DEST to an incomplete filename (for example, +data), and whenever a command is executed that must create a database file in DB_CREATE_FILE_DEST, the file is created in the designated disk group and assigned a unique fully qualified name. You can use an incomplete filename in other *_DEST initialization parameters.

Fully qualified File Name Form

A fully qualified form can be used for referencing existing Oracle ASM files in Oracle ASM operations, except for disk group creation. This form is the Oracle ASM file name that Oracle ASM automatically generates when an Oracle ASM file is created.

A fully qualified file name has the following form:

+diskgroup/dbname/filetype/filetypetag.file.incarnation

Where:

• +diskgroup is the disk group name preceded by a plus sign.

  You can think of the plus sign (+) as the root directory of the Oracle ASM file system, similar to the slash (/) on UNIX or Linux computers.

• dbname is the DB_UNIQUE_NAME of the database to which the file belongs.

• filetype is the Oracle file type and can be one of the file types shown in Table 7-3.

• filetypetag is type specific information about the file and can be one of the tags shown in Table 7-3.

• file.incarnation is the file/incarnation pair, used to ensure uniqueness.

An example of a fully qualified Oracle ASM filename is:

+data/orcl/controlfile/Current.256.541956473

Alias Oracle ASM Filename Forms

Alias Oracle ASM filenames can be used both for referencing existing Oracle ASM files and for creating new Oracle ASM files. Alias names start with the disk group name preceded by a plus sign, after which you specify a name string. Alias filenames are implemented using a hierarchical directory structure, with the slash (/) or backslash (\) character separating name components. You can create an alias in any Oracle ASM directory generated by Oracle-Managed Files (system-generated) or created by a user. An alias must include the disk group name; you cannot create an alias at the root level (+).

When you create an Oracle ASM file with an alias filename, the file is created with a fully qualified name, and the alias filename is additionally created. You can then access the file with either name.

Alias Oracle ASM filenames are distinguished from fully qualified filenames or numeric filenames because they do not end in a dotted pair of numbers. It is an error to attempt to create an alias that ends in a dotted pair of numbers, such as in the format USERS.259.685366091. Examples of Oracle ASM alias filenames are:

Oracle Database references database files by their alias filenames, but only if you create the database files with aliases. If you create database files without aliases and then add aliases later, the database references the files by their fully qualified filenames. The following are examples of how the database uses alias filenames:

• Alias filenames appear in V$ views. For example, if you create a tablespace and use an alias filename for the data file, the V$DATAFILE view shows the alias filename.

• When a control file points to data files and online redo log files, it can use alias filenames.

• The CONTROL_FILES initialization parameter can use the alias filenames of the control files. The Database Configuration Assistant (DBCA) creates control files with alias filenames.

For more information about alias filenames, see "Managing Alias Names for Oracle ASM Filenames".

CREATE UNDO TABLESPACE myundo 
     DATAFILE '+data(my_undo_template)/orcl/my_undo_ts' SIZE 200M; 

ALTER DISKGROUP data DROP FILE '+data/orcl/my_undo_ts';

Alias Oracle ASM Filename with Template Form

An alias Oracle ASM filename with template is used only for Oracle ASM file creation operations. It has the following format:

+diskgroup(templatename)/alias

Alias filenames with template behave identically to alias filenames except that a file created with an alias filename with template receives the attributes specified by the named template. The template must belong to the disk group that the file is being created in. See Example 7-1.

The creation and maintenance of Oracle ASM templates is discussed in "Managing Disk Group Templates".

An example of an alias Oracle ASM filename with template is:

+data(mytemplate)/config1

Explicitly specifying a template name, as in the previous example, overrides the system default template for the type of file being created.

Incomplete Oracle ASM Filename Form

Incomplete Oracle ASM filenames are used only for file creation operations and are used for both single and multiple file creation. They consist only of the disk group name. Oracle ASM uses a system default template to determine the Oracle ASM file mirroring and striping attributes. The system template that is used is determined by the file type that is being created. For example, if you are creating a data file for a tablespace, the DATAFILE template is used.

An example of using an incomplete Oracle ASM filename is setting the DB_CREATE_FILE_DEST initialization parameter to:

+data

With this setting, every time you create a tablespace, a data file is created in the disk group data, and each data file is assigned a different fully qualified name. See "Creating Oracle ASM Files Using a Default File Location for Disk Group Specification" for more information.

Incomplete Oracle ASM Filename with Template Form

Incomplete Oracle ASM filenames with templates are used only for file creation operations and are used for both single and multiple file creation. They consist of the disk group name followed by the template name in parentheses. When you explicitly specify a template in a file name, Oracle ASM uses the specified template instead of the default template for that file type to determine attributes for the file.

An example of using an incomplete Oracle ASM filename with template is setting the DB_CREATE_FILE_DEST initialization parameter to:

+data(mytemplate)

Creating Oracle ASM Files Using a Default File Location for Disk Group Specification

Using the Oracle Managed Files feature for operating system files, you can specify a directory as the default location for the creation of data files, temporary files, redo log files, and control files. Using the Oracle Managed Files feature for Oracle ASM, you can specify a disk group, in the form of an incomplete Oracle ASM filename, as the default location for creation of these files, and additional types of files, including archived log files. As for operating system files, the name of the default disk group is stored in an initialization parameter and is used whenever a file specification (for example, DATAFILE clause) is not explicitly specified during file creation.

The following initialization parameters accept the multiple file creation context form of Oracle ASM filenames as a destination:

• DB_CREATE_FILE_DEST

  Specifies the default disk group location in which to create data and temp files.

• DB_CREATE_ONLINE_LOG_DEST_n

  Specifies the default disk group location in which to create redo log and control files.

• DB_RECOVERY_FILE_DEST

  Specifies a default disk group for a fast recovery area that contains a copy of the control file and redo log files if this parameter is specified and DB_CREATE_ONLINE_LOG_DEST_n and CONTROL_FILES are not specified.

• CONTROL_FILES

  Specifies a disk group in which to create control files.

The following initialization parameters accept the multiple file creation context form of the Oracle ASM filenames and Oracle ASM directory names as a destination:

• LOG_ARCHIVE_DEST_n

  Specifies a default disk group or Oracle ASM directory as destination for archiving redo log files

• LOG_ARCHIVE_DEST

  Optional parameter to use to specify a default disk group or Oracle ASM directory as destination for archiving redo log files. Use when specifying only one destination.

• STANDBY_ARCHIVE_DEST

  Relevant only for a standby database. It specifies a default disk group or Oracle ASM directory that is the location of archive logs arriving from a primary database. Not discussed in this book. This parameter has been deprecated. See Oracle Data Guard Concepts and Administration.

The following CREATE TABLESPACE SQL statement illustrates how an Oracle ASM file, in this case a data file, might be created in a default disk group. This example assumes that the DB_CREATE_FILE_DEST initialization parameter has been set to +data.

SQL> CREATE TABLESPACE mytblspace;

Oracle ASM automatically creates and manages the data file for mytblspace on Oracle ASM disks in the disk group data. File extents are stored using the attributes defined by the default template for a data file.

Using Oracle ASM Filenames in SQL Statements

You can specify Oracle ASM filenames in the file specification clause of your SQL statements. If you are creating a file for the first time, use the creation form of an Oracle ASM filename. If the Oracle ASM file exists, you must use the reference form of the filename, and if you are trying to re-create the file, you must add the REUSE keyword so that the space is reused for the new file. This usage might occur when, for example, trying to re-create a control file, as shown in "Creating Control Files in Oracle ASM".

If a reference form is used with the REUSE keyword and the file does not exist, an error results.

Example 7-2 an example of specifying an Oracle ASM filename in a SQL statement. In this case, it is used in the file creation form.

CREATE TABLESPACE mytblspace DATAFILE '+data' SIZE 200M AUTOEXTEND ON;

The tablespace mytblspace is created and is comprised of one data file of size 200 MB contained in the disk group data. The data file is set to auto-extensible with an unlimited maximum size. An AUTOEXTEND clause can be used to override this default.

For more examples of the use of Oracle ASM filename in SQL statements, see Appendix A, "Creating Database Files in Oracle ASM Using SQL*Plus".

Adding an Alias Name for an Oracle ASM Filename

Use the ADD ALIAS clause of the ALTER DISKGROUP statement to create an alias name for an Oracle ASM filename. The alias name must consist of the full directory path and the alias itself.

Example 7-3 adds a new alias name for a system-generated file name.

ALTER DISKGROUP data ADD ALIAS '+data/orcl/second.dbf'
     FOR '+data/orcl/datafile/mytable.342.123456789';

Renaming an Alias Name for an Oracle ASM Filename

Use the RENAME ALIAS clause of the ALTER DISKGROUP statement to rename an alias for an Oracle ASM filename. The old and the new alias names must consist of the full directory paths of the alias names.

Example 7-4 renames an alias.

ALTER DISKGROUP data RENAME ALIAS '+data/orcl/datafile.dbf'
     TO '+data/payroll/compensation.dbf';

Renaming an alias does not update the database reference to the alias.

Dropping an Alias Name for an Oracle ASM Filename

Use the DROP ALIAS clause of the ALTER DISKGROUP statement to drop an alias for an Oracle ASM filename. The alias name must consist of the full directory path and the alias itself. The underlying file to which the alias refers is unchanged.

Example 7-5 drops an alias.

ALTER DISKGROUP data DROP ALIAS '+data/payroll/compensation.dbf';

Example 7-6 fails because it attempts to drop a system-generated filename and this syntax is not allowed.

ALTER DISKGROUP data 
     DROP ALIAS '+data/orcl/datafile/mytable.342.123456789';

Dropping Files and Associated Aliases from a Disk Group

You can delete Oracle ASM files and their associated aliases from a disk group using the DROP FILE clause of the ALTER DISKGROUP statement. You must use a fully qualified filename, or an alias name when specifying the file to delete. The underlying file on the file system is not dropped when the alias is dropped.

Some reasons why you may want to delete files include:

• A file created using aliases is not an Oracle Managed File. Consequently, it is not automatically deleted.

• A point-in-time-recovery of a database might restore the database to a time before a tablespace was created. The restore does not delete the tablespace, but there is no reference to the tablespace or its data file in the restored database. You could manually delete the data file.

In Example 7-7, the alias name for the file is used to delete both the file and the alias from a disk group.

ALTER DISKGROUP data DROP FILE '+data/payroll/compensation.dbf';

In Example 7-8, the Oracle-Managed Files (system-generated) file name is used to drop the file and any associated alias.

ALTER DISKGROUP data
     DROP FILE '+data/orcl/datafile/mytable.342.123456789';

Creating a New Directory

Use the ADD DIRECTORY clause of the ALTER DISKGROUP statement to create a hierarchical directory structure for alias names for Oracle ASM files. Use the slash (/) or backslash (\) character to separate components of the directory path. The directory path must start with the disk group name, preceded by a plus sign (+), followed by any subdirectory names of your choice.

The parent directory must exist before attempting to create a subdirectory or alias in that directory. A directory must be created below the disk group level.

Example 7-9 creates a hierarchical directory for disk group data, which can contain, for example, the alias name +data/orcl/control_file1.

ALTER DISKGROUP data ADD DIRECTORY '+data/orcl';

Assuming no subdirectory exists under the directory +data/orcl, the SQL statement fails in Example 7-10.

ALTER DISKGROUP data
     ADD DIRECTORY '+data/orcl/first_dir/second_dir';

Renaming a Directory

The RENAME DIRECTORY clause of the ALTER DISKGROUP statement enables you to rename a directory. System-created directories (those containing system-generated names) cannot be renamed. The root level (disk group name) cannot be renamed.

Example 7-11 renames a directory.

ALTER DISKGROUP data RENAME DIRECTORY '+data/mydir'
     TO '+data/yourdir';

Dropping a Directory

You can delete a directory using the DROP DIRECTORY clause of the ALTER DISKGROUP statement. You cannot drop a system-created directory. You cannot drop a directory containing alias names unless you also specify the FORCE clause.

Example 7-12 deletes a directory along with its contents.

ALTER DISKGROUP data DROP DIRECTORY '+data/yourdir' FORCE;

Inside /sys/asm

The Oracle ASM virtual folder is created by default during XML DB installation. If the database is not configured to use Oracle ASM, the folder is empty and no operations are permitted on it.

The Oracle ASM virtual folder contains folders and subfolders that follow the hierarchy defined by the structure of an Oracle ASM fully qualified file name. Figure 7-1 illustrates an example of this hierarchy, which for simplicity, excludes directories created for aliases.

The folder /sys/asm contains one subfolder for every mounted disk group, and each disk group folder contains one subfolder for each database that uses the disk group. In addition, a disk group folder might contain files and folders corresponding to aliases created by the administrator. Continuing the hierarchy, the database folders contain file type folders, which contain the Oracle ASM files.

Figure 7-1 Hierarchical Structure of Oracle ASM Folders in an XML DB Installation

Description of "Figure 7-1 Hierarchical Structure of Oracle ASM Folders in an XML DB Installation"

The following are usage restrictions on /sys/asm:

• You cannot create hard links to existing Oracle ASM files or directories with APIs such as DBMS_XDB.LINK.

• You cannot rename (move) an Oracle ASM file to another disk group or to a directory outside Oracle ASM.

You can use the directory /sys/asm for storing the names of disk groups. You cannot store other files in this directory. Within the disk group directories under /sys/asm, such as /sys/asm/DATA, you can only store database files in these sub-directories. Oracle ASM rejects attempts to store non-database files in these directories.

Template Attributes

Table 7-4 shows the permitted striping attribute values and allocation unit size chunks. These values correspond to the STRIPE column of V$ASM_TEMPLATE.

Table 7-5 shows the permitted redundancy values for Oracle ASM templates. These values correspond to the REDUND column of V$ASM_TEMPLATE.

Table 7-6 shows the initial attribute settings for the default templates. The type of mirroring associated with the Mirroring column for normal, high, and external redundancy disk groups is specified in Table 7-5. For example, the Mirror column for high redundancy disk groups displays MIRROR in Table 7-6. In Table 7-5, the MIRROR value for high redundancy disk groups corresponds to Three-way mirroring.

Table 7-7 shows the permitted primary and mirror region values for Oracle ASM templates. These values correspond to the PRIMARY_REGION and MIRROR_REGION columns of V$ASM_TEMPLATE. For more information about disk regions, see "Intelligent Data Placement".

Adding Templates to a Disk Group

To add a template to a disk group, use the ADD TEMPLATE clause of the ALTER DISKGROUP statement.

If the name of your new template is not listed in Table 7-6, then it is not used as a default template for database file types. To use the template, you must reference its name when creating a file.

When adding a template to a disk group, the attributes are optional. If no redundancy attribute is specified, the value defaults to MIRROR for a normal redundancy disk group, HIGH for a high redundancy disk group, and UNPROTECTED for an external redundancy disk group. If you do not specify a striping attribute, then the value defaults to COARSE. If you do not specify a value for the primary or mirror region attributes, then the value defaults to COLD and MIRRORCOLD respectively.

Example 7-13 creates a new template named reliable for the normal redundancy disk group data.

ALTER DISKGROUP data ADD TEMPLATE reliable ATTRIBUTES (HIGH FINE);

Example 7-14 creates a new template named unreliable that specifies files are to be unprotected (no mirroring).

ALTER DISKGROUP data ADD TEMPLATE unreliable ATTRIBUTES (UNPROTECTED);

Modifying a Disk Group Template

The MODIFY TEMPLATE clause of the ALTER DISKGROUP statement enables you to modify the attribute specifications of an existing system default or user-defined disk group template. Only specified template attributes are changed. Unspecified properties retain their current value. When you modify an existing template, only new files created by the template reflect the attribute changes. Existing files maintain their attributes.

Example 7-15 changes the striping attribute specification of the reliable template for disk group data.

ALTER DISKGROUP data MODIFY TEMPLATE reliable 
     ATTRIBUTES (COARSE);

Dropping Templates from a Disk Group

Use the DROP TEMPLATE clause of the ALTER DISKGROUP statement to drop one or more templates from a disk group. You can only drop templates that are user-defined; you cannot drop system default templates.

Example 7-16 drops the previously created template unreliable from data:

ALTER DISKGROUP data DROP TEMPLATE unreliable;

Creating Tablespaces in Oracle ASM: Specifying Attributes with Templates

Use the SQL ALTER SYSTEM and CREATE TABLESPACE statements to create a tablespace that uses a user-defined template to specify the attributes of the data file.

Example 7-17 assumes that the template (mytemplate) has been defined.

ALTER SYSTEM SET DB_CREATE_FILE_DEST = '+data(mytemplate)';

CREATE TABLESPACE mytblspace;