6 Creating RAC Databases with the Database Configuration Assistant

6.1 Using Database Configuration Assistant with Oracle Real Application Clusters

DBCA has the following primary functions:

• Create the database and its instances

• Set up network configuration for database, instances and database services

• Configure Enterprise Manager Grid Control

• Start up the database, its instances, services, and any other node applications

  
  

  See Also: "Creating the Database after Installation Using Database Configuration Assistant" for more information about using DBCA in standalone mode Oracle Database Net Services Administrator's Guide if you experience problems, for example, with the listener configuration, and for further information about Lightweight Directory Access Protocol (LDAP)-compliant directory support

  
  

6.2 Benefits of Using Database Configuration Assistant

Oracle recommends that you use Database Configuration Assistant (DBCA) to create your RAC database, because DBCA's preconfigured databases optimize your environment for features such as ASM, the server parameter file, and automatic undo management. DBCA also provides pages to create new ASM disk groups if they are needed; if you use ASM or cluster file system storage, then DBCA also configures recovery and backup disk space.

With DBCA, you can create site-specific tablespaces as part of database creation. If you have datafile requirements that differ from those offered by DBCA templates, then create your database with DBCA and modify the datafiles later. You can also run user-specified scripts as part of your database creation process.

DBCA also configures your RAC environment for various Oracle high availability features, such as services and cluster administration tools. It also starts any database instances required to support your defined configuration.

6.3 Oracle Real Application Clusters High Availability Services

When you configure high availability services with the DBCA Database Services page, you can also configure service instance preferences and Transparent Application Failover (TAF) policies.

6.4 Verifying Requirements for DBCA

To help to verify that your system is prepared to create the Oracle Database with RAC successfully, enter a Cluster Verification Utility command using the following command syntax:

cluvfy stage -pre dbcfg -n node_list -d oracle_home [-verbose]

In the preceding syntax example, the variable node_list is the list of nodes in your cluster, separated by commas, and the variable oracle_home is the path for the Oracle home under which the database is to be created or its configuration is to modified.

For example, to perform a check to determine if your system is prepared for an Oracle Database with RAC on a two-node cluster with nodes node1 and node2, and with the Oracle home path c:\oracle\product\10.2.0, enter the following command:

cluvfy stage -pre dbcfg -n node1,node2 -d c:\oracle\product\10.2.0

You can select the option -verbose to receive progress updates as the CVU performs its system checks, and detailed reporting of the test results.

If the Cluster Verification Utility summary indicates that the cluster verification check fails, then review and correct the relevant system configuration steps, and run the test again.

The command cluvfy stage -pre dbcfg verifies the following:

• Node Reachability: All the specified nodes are reachable from the local node

• User Equivalence: User equivalence exists on all the specified nodes

• Node Connectivity: The connectivity exists between all the specified nodes through the available public and private network interfaces

• Administrative Privileges: The oracle user has proper administrative privileges on the specified nodes for creating a RAC database

• Oracle Clusterware Integrity: All the components of the Oracle Clusterware stack are operational

6.5 Creating the Database after Installation Using Database Configuration Assistant

To create a database with DBCA in standalone mode without ASM or a cluster file system, you must already have configured each raw device as described in Appendix C. In addition, you must already have run Oracle Net Configuration Assistant to configure your Oracle Net listener.ora file.

If you plan to use ASM storage, then you must already have created logical partitions without primary partitions on the same drive, and deleted the drive letters for these partitions on all nodes, or used DBCA to mark partitions.

If you select DBCA templates that use preconfigured datafiles and if you do not use ASM or a cluster file system, then during database creation, DBCA first verifies that you created the raw devices for each tablespace. If you have not configured the raw devices, then you must configure the raw devices and replace the default datafile names that DBCA provides with raw device names on the DBCA Storage page to continue database creation.

To start DBCA, click Start, and select Programs, Oracle - Oracle_home name, Configuration and Migration Tools, then Database Configuration Assistant

6.6 Creating an Oracle Real Application Clusters Database with DBCA

When you start DBCA, the first page it displays is the Welcome page for RAC, which includes the option to select an Oracle Real Application Clusters (RAC) database. Note that you will not see this page if the Oracle home from which you are running DBCA was not installed in a cluster environment.

If DBCA does not display the Welcome page for RAC, then DBCA was unable to detect whether the Oracle home is cluster-installed. In this case, check that the OUI inventory is correctly located in c:\Program Files\oracle\Inventory, and that the files in the Oracle inventory directory are not corrupted. Also, perform clusterware diagnostics by running the CVU command cluvfy stage -post crsinst -n nodename.

If the RAC welcome page opens, then complete the following steps to create a RAC database:

1. On the Welcome page, select Real Application Clusters database and click Next.

2. DBCA displays the Operations page.

   Note that DBCA enables the options Configure Database Options, Delete a Database, Instance Management, Configure Automatic Storage Management, and Services Management options only if there is at least one RAC database configured on your cluster that runs from the Oracle home.

   Select Create a Database, and click Next.

3. DBCA displays the Node Selection page. DBCA highlights the local node by default. Select the other nodes that you want to configure as members of your cluster database, and click Next.

   
   

   Note: If nodes that are part of your cluster installation do not appear on the Node Selection page, then run the CVU to perform inventory diagnostics and clusterware diagnostics.

   
   

4. DBCA displays the Database Templates page. The predefined template choices on the Database Templates page are Custom Database, Data Warehouse, General Purpose, and Transaction Processing.

   Use one of the predefined templates, which include datafiles, if you want to create database with specifically configured options. The Custom Database template does not include datafiles or options specially configured for a particular type of application.

   Select the template from which you wish to create your cluster database, and click Next.

5. DBCA displays the Database Identification page. Provide a unique global database domain name for your database (typically in the form of "database.acme.com.") The Oracle system identifier (SID) prefix is generated automatically from the name you provide. You can either use the automatically generated SID, or create your own. When you are finished, click Next.

   
   

   Note: The global database name can be up to 30 characters in length, and must begin with an alphabetical character. The SID prefix must begin with an alphabetical character. The maximum number of characters you can use for the SID prefix depends on the number of nodes in the RAC database. If the RAC database contains from one to nine nodes, then the SID prefix can be no more than 61 characters on Windows-based systems. If the RAC database contains from 10 to 99 nodes, then the SID prefix can be no more than 6 characters. DBCA uses the SID prefix to generate a unique value for the variable ORACLE_SID for each instance.

   
   

6. The Management Options page appears. Select whether you will enable management through Oracle Enterprise Manager.

   If you select Enterprise Manager with the Grid Control option and DBCA discovers agents running on the local node, then you can select the preferred agent from a list.

   After you select the Database Control option, you can set up E-mail notification and enable daily backups. For E-mail notifications, you provide the outgoing mail server and E-mail address. For daily backups, you enter the backup time and operating system credentials for the user that performs backup.

   When you have finished, click Next.

7. The Database Credentials page appears. Enter the passwords for your database on the Database Credentials page. You can enter the same or different passwords for the administrative users SYS and SYSTEM, and also, if you selected Enterprise Manager on the Management Options page, the monitoring accounts DBSNMP and SYSMAN. Select the option Use the Same Password for All Accounts to assign the same password to all of the listed users, or provide a different password for each of these users by selecting the option Use Different Passwords.

   When you have entered the password information, click Next. DBCA displays the Storage Options page.

8. The Storage Options page appears. Use the Storage Options page to select a storage type for database creation. The Cluster File System option is the default. Select a storage option and click Next to proceed to the next page.

   If you selected Cluster File System, then the next page that appears is the Database File Locations page, described in Step 9.

   If you select Raw Devices, then the next page that appears is the Recovery Configuration page, described in Step 10.

   If you select Automatic Storage Management (ASM), then provide additional information as follows:

   1. If there is not an ASM instance on any of the cluster nodes, then DBCA displays the Create ASM Instance page for you, described in Step c. Otherwise DBCA displays the ASM Disk Groups page, described in Step d.

   2. If an ASM instance exists on the local node, then DBCA displays a dialog asking you to enter the password for the SYS user for ASM.

   3. To initiate the creation of the required ASM instance, supply the password for the SYS user of the ASM instance. If your Oracle home is installed on cluster file system, then the ASM instance uses an SPFILE; otherwise, you can select either an IFILE or an SPFILE on shared storage for the instances. After you enter the required information, click Next to create the ASM instance. When the instance is created, DBCA proceeds to the ASM Disk Groups page described in Step d.

   4. From the ASM Disk Groups page, you can create a new disk group, add disks to an existing disk group, or select a disk group for your database storage.

      If you have just created a new ASM instance, then there will be no disk groups from which to select, so you must create a new one by clicking Create New to open the Create Disk Group page, described in Step e.

      Similarly, if one or more disk groups are displayed but you want to add a new one, then click Create New and follow the procedure described in Step e to complete the Create Disk Group page.

      If you want to use an existing disk group but wish to add more disks to it, click Add Disks and follow the instructions in Step f.

      Once you are satisfied with the ASM disk groups available to you, select the one you wish to use for your database files and click Next to proceed to the Database File Locations page, described in step 9.

      
      

      Note: To use a flash recovery area, Oracle recommends that you create two separate ASM disk groups: one for the database area and one for the recovery area.

      
      
      
      

      See Also: Oracle Database Concepts for more information about using a flash recovery area

      
      

   5. Enter the disk group name and then click the redundancy level for the group if you do not wish to use the default value (Normal). Create your disk group by selecting from the list of candidate disks. Continue by following the process described in Step g.

   6. If there is a disk group that you want to use but you want to add more disks to it, then select the group and click Add Disks. Add to the disk group by selecting from the list of candidate disks. Continue by following the process described in Step g.

   7. If you do not see the disks you wish to add, click Change Disk Discovery Path to alter the search path used by DBCA to find available disks. You can select disks with a status of Candidate or Former (never used in an ASM disk group or no longer in a group) by checking the select box. If you select a disk that has an ASM disk header, but the disk group is no longer in use (because of an aborted install, a de-install, and so on), then you must also check the Force column to override the header. When you have selected the desired disks, click OK to add them to your disk group and return to the ASM Disk Groups Page. To proceed, see the instructions described earlier in Step d.

   8. If DBCA displays the following message:

      The file oracle_home\bin\oracle does not exist on nodes node_list. 
      Make sure that file exists on these nodes before proceeding.
      
      

      then the Oracle home from which the first ASM instance in the cluster runs is not installed on these cluster nodes. You must extend the ASM Oracle home to these nodes by performing the procedure documented in "Step 4: Adding Nodes at the Oracle RAC Database Layer" in the Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide. However, do not perform Step 5 in that section. The OUI extends the ASM Oracle home to the selected nodes and performs any configuration required for running an ASM instance on these nodes.

   9. If DBCA displays the message Please run the DBCA from one of the nodes that has an existing ASM instance node_list., then you are attempting to create a RAC database using ASM storage and the ASM instance does not exist on the node from which you ran DBCA. However, ASM instances do exist on the remote nodes that appear in the message node list. In this case, DBCA cannot clone the existing ASM instance from the remote node to the local node. To correct this, start DBCA from one of the nodes shown in the node list to create your RAC database using ASM storage. This copies the local node's ASM instance and modifies its parameters and attributes to create ASM instances on the nodes in your cluster that do not have ASM instances.

   10. If DBCA displays the message ORACLE_BASE for ASM home asm_home does not match the value for database home db_home. Please set ORACLE_BASE to asm_home and restart DBCA., then this means that you selected a node to be part of your RAC database that does not have an ASM instance. In addition, the ASM instance on the local node is running from an Oracle home that is different from the Oracle home for the database to be created. Both the ASM home and the database home must be under a common ORACLE_BASE. If you created the original ASM instance without setting ORACLE_BASE, then set the ORACLE_BASE to the asm_home and restart DBCA to proceed.

9. The Database File Locations page appears. The Database File Locations page enables you to specify a location where the database datafiles are created. Select one of the following options:

   • Use Database File Locations from Template: Select this option to allow the database file location to be determined by the Oracle database template type that you selected in step 4.

   • Use Common Location for All Database Files: Select this option if you want to use a file system. The files will not be managed by Oracle. You can enter a path on which you want database datafiles to be placed, or click Browse to locate a path.

   • Use Oracle-Managed Files: Select this option if you want your files to be managed using ASM. If you do not select the Database File Locations from Template option, then you can enter an existing ASM disk group name or directory path name in the Database Area field, or click Browse to open a selection list.

   If you want to multiplex the database redo log files and control files, then click Multiplex Redo Logs and Control Files, and provide the location for each copy you want. Click OK when you have defined the multiplex locations to return to the Database File Locations page.

   You may also define your own variables for the file locations if you plan to use the Database Storage page, explained in Step 14, to define individual file locations.

10. The Recovery Configuration page appears. If you are using ASM or NAS storage, then you can also select the flash recovery area and size on the Recovery Configuration page. If you are using ASM, then the flash recovery area defaults to the ASM Disk Group. If you are using OCFS, then the flash recovery area defaults to %ORACLE_BASE%\flash_recovery_area.

    You can select redo log archiving by clicking the Enable Archiving check box.

    You may also define your own variables for the file locations if you plan to use the Database Storage page, explained in Step 14, to define individual file locations.

    When you have completed your entries, click Next. The Database Content page is displayed.

11. The Database Content page appears. On the Database Content page, if you chose the Custom Database option, you can select or deselect the database components and their corresponding tablespace assignment. For a seed database, you can select whether to include the sample schemas in your database and to run custom scripts as part of the database creation processing. After completing your selections, click Next.

12. The Database Services page appears. To create services on the Database Services page, expand the Services tree. Oracle displays the global database name in the top left-hand corner of the page. Select the global database name and click Add to add services to the database. Enter a service name in the Add a Service dialog and click OK to add the service and return to the Database Services page.

    The service name appears under the global database name. Select the service name and DBCA displays the service preferences for the service on the right-hand side of the DBCA Database Services page. Change the instance preference (Not Used, Preferred, or Available) and TAF policies for the service as needed.

    Repeat this procedure for each service and when you are done configuring services for your database, click Next. DBCA displays the Initialization Parameters page.

13. The Initialization Parameters page appears. By default, the Initialization Parameters page shows only the basic parameters, and only enables you to change the parameter file definition if you are using raw storage. Each tab on the Initialization Parameters page provides different sets of information that you can add or modify as follows:

    1. Memory Tab: Click Typical for default values based on the database type you selected or Custom to set your own values for the memory parameters. You can also see values for the advanced parameters by clicking All Initialization Parameters. This causes the All Initialization Parameters table to appear

       Carefully review the parameter settings displayed in the table, as DBCA configures these settings in your server parameter file. Instance-specific parameter settings for your RAC database appear at the bottom of the table. The SID prefixes for these entries appear in the Instance column, on the left side of the table.

       To review the instance-specific parameter settings, scroll downward using the scroll bar on the right side of the table. Use the check box in the Override Default column to indicate whether DBCA should place the parameter setting in your server parameter file. DBCA only places a parameter entry into the server parameter file if the entry displays a check mark in the Override Default column of the All Initialization Parameters table.

       
       

       Notes: You cannot modify the SID in the Instance columnYou can alter self-tuning parameters with this dialog. However, setting these parameters to inappropriate values may disable the Oracle self-tuning features.You cannot specify instance-specific values for global parameters with DBCA. You should set the value of the CLUSTER_DATABASE_INSTANCES parameter to the number of instances you intend to use in the cluster if you are not including all the related nodes during the current execution of DBCA. If your global database name is longer than eight characters, then the database name value (in the db_name parameter) is truncated to the first eight characters and the DB_UNIQUE_NAME parameter value is set to the global name.

       
       

    2. Sizing Tab: Use this page to select the database standard block size and process count.

    3. Character Sets Tab: Use this page to set the database character set value.

    4. Connection Mode Tab: You can use this tab to select either dedicated or shared database connections to your database.

    5. Parameter File Tab: This tab will only appear if you are using raw storage. Use this tab to enter a raw device name for the location of the server parameter file.

    When you have completed all your work on the Initialization Parameters page, click Next.

14. The Database Storage page appears.

    If you selected a preconfigured database template, such as the General Purpose template, then DBCA displays the control files, datafiles, and redo logs on the Database Storage page. Select the folder and the file name underneath the folder to edit the file name.

    If you selected the Custom Database template (the template without datafiles), then DBCA displays the control files, tablespaces, datafiles, and redo logs. To change the tablespace properties, such as the datafile or the tablespace size, click the tablespaces icon to expand the object tree on the left-hand side of the page and click the tablespace. The tablespace property dialog appears on the right-hand side. Make your changes and click OK.

    When entering file names in the Database Storage page for raw storage, note the following

    • If you have not set the DBCA_RAW_CONFIG environment variable, then DBCA displays default datafile names. You must override these names to provide raw device names on this page for each control file, datafile, and redo log group file.

    • For Windows-based platforms, if the default symbolic links exist and you have not set the DBCA_RAW_CONFIG environment variable, then DBCA replaces the default datafiles with these symbolic link names and displays them in the Database Storage page. If the symbolic links do not exist, then DBCA displays the default file system datafile file names on the Database Storage page. In this case, replace the default datafile file names with the symbolic link names.

    After you complete your entries on the Database Storage page, click Next.

15. The Creation Options page appears. Select one of the following database options, and click Finish.

    • Create Database—Creates the database

    • Save as a Database Template—Creates a template that records the database structure, including user-supplied inputs, initialization parameters, and so on. You can later use this template to create a database. DBCA only displays this option if you selected the Custom Database template.

    • Generate Database Creation Scripts—Generates database creation scripts.

    After you click Finish, DBCA displays a Summary dialog.

16. Review the Summary dialog information and click OK to create the database.

After you complete Step 16 DBCA:

• Creates an operative RAC database and its instances

• Creates the RAC data dictionary views

• Configures the network for the cluster database

• Starts the Oracle services if you are on a Windows-based platform

• Starts the listeners and database instances and then starts the high availability services

6.7 Deleting a Real Application Clusters Database with DBCA

This section explains how to delete a RAC database with DBCA. This process deletes a database and removes a database's initialization parameter files, instances, OFA structure, and Oracle network configuration. However, this process does not remove datafiles if you placed the files on raw devices or on raw partitions.

To delete a database with DBCA:

1. Start DBCA on one of the nodes:

   On Windows-based platforms, click Start, and select Programs, Oracle - Oracle_home name, Configuration and Migration Tools, then Database Configuration Assistant

   The DBCA Welcome page appears.

2. Select Oracle Real Application Clusters and click Next.

   After you click Next, DBCA displays the Operations page.

3. Select Delete a database, click Next. DBCA displays the List of Cluster Databases page.

4. If your user ID and password are not operating-system authenticated, then the List of Cluster Databases page displays the user name and password fields. If these fields appear, then enter a user ID and password that has SYSDBA privileges.

   
   

   See Also: "Database Password and Role Management in Real Application Clusters" on page B-19

   
   

5. Select the database to delete and click Finish.

   After you click Finish, DBCA displays a dialog to confirm the database and instances that DBCA is going to delete.

6. Click OK to begin the deletion of the database and its associated files, services, and environment settings, or click Cancel to stop the operation.

When you click OK, DBCA continues the operation and deletes all of the associated instances for this database. DBCA also removes the parameter files, password files, and oratab entries.

At this point, you have accomplished the following:

• Deleted the selected database from the cluster

• Deleted the selected database's Oracle services for Windows-based platforms

• Deleted high availability services that were assigned to the database

• Deleted the Oracle Net configuration for the database

• Deleted the OFA directory structure from the cluster

• Deleted the datafiles if the datafiles were not on raw devices