Skip Headers
Oracle® Real Application Clusters Installation Guide
11g Release 1 (11.1) for Linux and UNIX

Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

3 Creating Oracle Real Application Clusters Databases with Database Configuration Assistant

This chapter describes how to use Database Configuration Assistant (DBCA) in standalone mode to create and delete Oracle Real Application Clusters (Oracle RAC) databases. The topics in this chapter include the following:

3.1 Using Database Configuration Assistant with Oracle RAC

DBCA has the following primary database functions:

In addition DBCA has the following primary ASM functions:

See Also:

  • "Creating an Oracle RAC Database with DBCA" for more information about using DBCA in standalone mode

  • Oracle Database Net Services Administrator's Guide to resolve problems—for example, with the listener configuration—and for further information about Lightweight Directory Access Protocol (LDAP)-compliant directory support

3.2 Benefits of Using Database Configuration Assistant

Oracle recommends that you use DBCA to create your Oracle RAC database, because preconfigured databases optimize your environment for features such as Automatic Storage Management (ASM), the server parameter file (SPFILE), 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 automated backup, which uses the Fast recovery area.

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

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

3.3 Automatic Listener Migration from Earlier Releases

If your system has an Oracle Database 10g (10. 1) installation, and you install Oracle Database 11g release 1 (11.1) either to coexist with or to upgrade the Oracle Database 10.1 or 10.2 installation, then most installation types automatically migrate the Oracle Database 10.1 listener to the 11g release 1 (11.1) Oracle home. During migration, they configure and start a default Oracle Net listener using the same TCP/IP port as the existing listener, with the IPC key value EXTPROC. This process occurs through one of the following scenarios:

The listener migration process stops the listener in the existing Oracle home, and restarts the listener from the new Oracle home. During migration, client applications may not be able to connect to any databases that are registered to the listener that is being migrated.

3.4 Verifying Requirements for DBCA

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

/CRS_home/bin/ stage -pre dbcfg -n node_list -d Oracle_home [-verbose]

In the preceding syntax example, the variable CRS_home is the Oracle Clusterware home, 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 directory where OUI creates or modifies the database.

For example, to perform a check to determine if your system is prepared for an Oracle Database with Oracle RAC installation on a two-node cluster with nodes node1 and node2, with the CRS home path/u01/app/crs/, and with the Oracle home path /u01/app/oracle/product/11.1/db1, enter the following command:

$ /u01/app/crs/bin/cluvfy stage -pre dbcfg -n node1,node2 -d\

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 CVU summary indicates that the cluster verification check fails, then review and correct the relevant system configuration steps, and run the test again.

The command stage -pre dbcfg verifies the following:

3.5 Creating an Oracle RAC Database with DBCA

To create a database with DBCA in standalone mode without ASM or a cluster file system, you must have configured shared storage devices. In addition, you must have run the Oracle Net Configuration Assistant (NETCA) to configure your Oracle Net listener.ora file.

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

To start DBCA, connect as the oracle user to one of your nodes where Oracle RAC is installed, load SSH keys into memory, and enter the command dbca command from the $ORACLE_HOME/bin directory.


In an Oracle RAC environment, you must load SSH keys into memory for the terminal session where you start DBCA. If you do not do this, then you receive user equivalency errors when you attempt to start DBCA. If you use a pass phrase on your system for SSH, then you must provide the pass phrase to load the SSH keys.

Use the following commands to load SSH keys:

$ exec /usr/bin/ssh-agent $SHELL
$ /usr/bin/ssh-add

Provide the pass phrase when prompted. You can then start DBCA.

When you start DBCA, the first page it displays is the Welcome page for Oracle RAC, which includes the option to select an Oracle RAC database. DBCA displays this Oracle RAC Welcome page only if the Oracle home from which it is started was installed on a cluster.

If the Oracle RAC Welcome page opens, then provide information as prompted by DBCA. Click Help if you need assistance.

If DBCA does not display the Welcome page for Oracle RAC, then DBCA was unable to detect if the Oracle home is installed on a cluster. In this case, check that the OUI inventory is correctly located in the directory /etc/oraInst.loc, and that the oraInventory file is not corrupted. Also, perform clusterware diagnostics by using the following CVU command syntax:

/CRS_home/bin/cluvfy/ stage -post crsinst -n nodelist.

For example, with the mountpoint /u01/app/crs, and nodes node1 and node2, run the following command:

$ /u01/app/crs/bin/ stage -post crsinst -n node1,node2

Note the following important information when using DBCA:

After you respond to DBCA prompts, review the Summary dialog information and click OK, DBCA does the following:


After you have created the database, if you decide that you want to install additional Oracle Database products in the database you have created, then you must stop all processes running in the Oracle home before you attempt to install the additional products, so that Oracle Universal Installer can relink certain executables and libraries. Refer to Appendix E, "How to Stop Processes in an Existing Oracle Real Application Clusters Database" for additional information.

3.6 Deleting an Oracle RAC Database with DBCA

This section explains how to delete an Oracle RAC database with DBCA. This process deletes a database and removes a database's initialization parameter files, instances, OFA structure, and an Oracle network configuration. However, this process does not remove data files 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:.

    • Run the DBCA command from the $ORACLE_HOME/bin directory.

    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, and 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 for a user account that has SYSDBA privileges.

  5. Select the database to delete, and click Finish.

    After you click Finish, DBCA displays a dialog box 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 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: