Creating a Database Using ASM Disk Group Locations

You can create a database that completely uses ASM disk group locations. You can do this when creating the database through the DBCA interface or if you are going to manually create the database. This topic describes both options.

Creating a Database Using ASM Disks with DBCA

If you are creating the database with the DBCA you will indicate that you wish to use ASM disks for the database as seen in this figure:

Following this screen, you will be prompted for the SYS password to the ASM instance. DBCA will then present to you a list of available disk groups that you can use to create the database as seen in this figure:

DBCA will then confirm your selection in the next screen. You will then be presented with a screen that asks you where you want the flash recovery area to be assigned to. It will pre-populate this screen with one of the disk groups that you selected to use in the previous screen (typically it will be the second disk group in the list). Here is a copy of the screen where we have selected out flash recovery area location:

The DBCA will set all of the different file location parameters to those in the ASM disk groups that you selected (e.g. CONTROL_FILES, DB_CREATE_FILE_DEST, DB_RECOVERY_FILE_DEST, and LOG_ARCHIVE_DEST_1). You can edit these choices if you wish to use a mix of ASM and cooked file systems.

You complete the DBCA screens as normal and DBCA will then create a database that is totally (or partially if you prefer) using ASM.

Creating a Database Using ASM Disks Manually

Creation of a database using ASM can actually be easier than creating a database with ASM if only because less typing is required. To create an Oracle database with ASM, follow the standard procedures, but when you are creating the parameter file make sure you assign the following parameters to an ASM disk group:


Once you have done this, issuing the create database command requires no parameters at all. Simply issue the command CREATE DATABASE. Oracle will create the various database files on ASM disk.