This chapter describes how to use Database Configuration Assistant (DBCA) in standalone mode to create and delete Oracle Real Application Clusters (Oracle RAC) databases.
See Also:Oracle Real Application Clusters Administration and Deployment Guide for information about using DBCA to add and delete instances
Oracle Database Configuration Assistant (DBCA) is a tool for creating and configuring an Oracle database.
DBCA has the following primary database functions:
Create and delete databases
Create database templates
Create, plug, unplug, and delete pluggable databases (PDBs)
Add and delete database instances
Register databases in Oracle Enterprise Manager Cloud Control
Configure and register database options (such as Oracle Database Vault) with the Directory Server
Note:Cluster Managed Services are no longer managed through DBCA. Instead, use the Cluster Managed Services page in Oracle Enterprise Manager Cloud Control, if available, or SRVCTL. For more information, see Oracle Real Application Clusters Administration and Deployment Guide.
Oracle Database Net Services Administrator's Guide to resolve problems—for example, with the listener configuration—and for more information about Lightweight Directory Access Protocol (LDAP)-compliant directory support
Oracle Database 2 Day + Real Application Clusters Guide for more information about using Oracle Enterprise Manager
Oracle recommends that you use Oracle Database Configuration Assistant (DBCA) to create your Oracle RAC database, because preconfigured databases optimize your environment for features such as the server parameter file (SPFILE), and automatic undo management.
DBCA enables you to create both policy-managed and administrator-managed databases. 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. DBCA also starts any database instances required to support your defined configuration.
You can use DBCA to create a database from templates supplied by Oracle, or from templates that you create. The templates contain settings optimized for a particular type of workload.
Oracle ships templates for the following two workload types:
General purpose or transaction processing
For more complex environments, you can select the Custom Database option. This option does not use templates and results in a more extensive interview, which means that it takes longer to create your database.
Click Show Details to see the configuration for each type of database. Select the template suited to the type of workload your database will support. If you are not sure which to choose, then select the default General Purpose or Transaction Processing template.
If your system has an Oracle Database 10g or 11g installation, and you install Oracle Database 12c Release 1 (12.1) either to coexist with or to upgrade the Oracle Database 10.1, 10.2, 11.1, or 11.2 installation, then most installation types automatically migrate the existing Oracle Database listener to the 12c Release 1 (12.1) Oracle home.
During migration, the upgrade process configures and starts a default Oracle Net listener using the same TCP/IP port as the existing listener, with the IPC key value. During the Oracle Clusterware upgrade, the default listener (
LISTENER_NODENAME) was migrated to the Oracle Grid Infrastructure home (Grid home). DBCA always uses the default listener.
The listener migration process stops the listener in the existing Oracle home, and restarts it in the new Oracle home. If the database was using the default listener (
LISTENER_NODENAME), then Oracle Net Configuration Assistant (NETCA) migrates the listener automatically to the Grid home as part of the Oracle Grid Infrastructure upgrade. If the database was using a nondefault listener, then Database Upgrade Assistant (DBUA) migrates the nondefault listener to the Oracle Database home.
Note:During migration, client applications might not be able to connect to any databases that are registered to the listener that is being migrated.
Use Cluster Verification Utility (CVU) to verify that your system is prepared for configuration changes.
Grid_home\bin\cluvfy stage -pre dbcfg -n node_list -d Oracle_home [-verbose]
You can select the option
-verbose to receive progress updates as CVU performs its system checks, and detailed reporting of the test results.
Example 3-1 Using CVU Prior to Verify Your System is Prepared for an Oracle RAC Installation
To verify that your system is prepared for an Oracle Database with Oracle RAC installation on a two-node cluster with nodes
node2, with the Grid home
C:\app\12.1.0\grid, and with the Oracle home path
C:\app\oracle\product\12.1.0\dbhome_1, enter the following command:
C:\app\12.1.0\grid\bin> cluvfy stage -pre dbcfg -n node1,node2 \ -d C:\app\oracle\product\12.1.0\dbhome_1
To create a database with DBCA, you must have run the Oracle Net Configuration Assistant (NETCA) to configure your Oracle Net
You no longer need to set the operating system environment variables
ORACLE_HOME to the Oracle RAC database home, or
ORACLE_UNQNAME to the database unique name.
Note:You can no longer set up email notification for Oracle RAC databases from either DBCA or OUI.
Before you can create an Oracle RAC database using Oracle Database Configuration Assistant, you must configure your system to meet the software requirements, if this was not done as part of the Oracle Grid Infrastructure installation.
The global database name for an Oracle RAC database must meet the naming requirements. The global database name consists of the database name and the domain name.
ORACLE_SIDvalues for each instance.
ORACLE_SIDfor each instance. The SID prefix must begin with an alphabetic character.
Before starting Oracle Database Configuration Assistant (DBCA) to configure an Oracle RAC database, you must install Oracle Grid Infrastructure for a cluster, and configure shared storage areas for Oracle RAC files.
Oracle Database Installation Guide for Microsoft Windows for more information about
Oracle Grid Infrastructure Installation Guide for your platform more information on shared storage configuration requirements
Oracle Automatic Storage Management Administrator's Guide for more information about creating disk groups
When you use Oracle Database Configuration Assistant to create an Oracle database or an Oracle RAC database, and specify an Oracle Home User during installation, then you need to enter the password for this user.
Figure 3-1 Specifying the Password for the Oracle Home User
See Also:Oracle Grid Infrastructure Installation Guide for Microsoft Windows x64 (64-Bit) for more information about the Oracle Home user.
When using DBCA to create and configure an Oracle RAC database, there are a few screens to navigate and several actions performed.
You can either start the Oracle Database Configuration Assistant (DBCA) utility from the command line or from the Windows Start menu.
Note:To run DBCA, you do not have to set operating system environment variables
ORACLE_HOMEto the Oracle RAC database home, or
ORACLE_UNQNAMEto the database unique name.
ORA_Homename_DBAgroup and must also be a member of
ORA_ASMDBAif Oracle ASM is used as storage for the Oracle RAC database.
Create Database on the Database Operation/Welcome page
Advanced Mode on the Creation Mode page
Oracle RAC database on the Database Template page
When you start DBCA, it automatically shows options for Oracle RAC if it detects from the central Oracle Inventory that the Oracle Home is enabled for Oracle RAC.
If DBCA does not detect the Oracle home as an Oracle RAC home, check that the OUI inventory is correctly located in the directory
C:\Program Files\Oracle\Inventory, and that the
oraInventory file is not corrupted. Also, perform clusterware diagnostics by using the following CVU command syntax:
Grid_home\bin\cluvfy\cluvfy.bat stage -post crsinst -n nodelist
When using DBCA, if nodes that are part of your cluster installation do not appear on the Node Selection page, then run the Opatch
lsinventory command to perform inventory diagnostics. Also use CVU to perform clusterware diagnostics.
Example 3-2 Performing Clusterware Diagnostics If DCBA Fails To Detect A Two-Node Cluster
If the Grid Home is
D:\app\12.1.0\grid, and the nodes are named
node2, then run the following command to perform clusterware diagnostics:
D:\app\12.1.0\grid\bin> cluvfy stage -post crsinst -n node1,node2
You can choose to use either Oracle ASM Disk groups or a shared file system as storage for Oracle RAC database files.
CLUSTER_DATABASE_INSTANCES parameter to the expected number of instances.
CLUSTER_DATABASE_INSTANCESto the total number of nodes that you plan to add to the cluster.
DB_NAMEparameter) is truncated to the first 8 characters, and the
DB_UNIQUE_NAMEparameter value is set to the global name.
See Also:Oracle Database Administrator's Guide for information about initialization parameters
Review this information to understand about Oracle Database Configuration Assistant (DBCA) actions during Oracle RAC database creation.
After you respond to DBCA prompts, review the Summary dialog information and click OK, DBCA performs several actions.
Creates an Oracle RAC database, and its instances
Creates the Oracle RAC data dictionary views
Starts the Oracle services if you are on a Windows-based platform
Starts the Oracle Clusterware high availability services
Starts the database instances across cluster nodes
After you have created the Oracle RAC database, if you decide to install additional Oracle Database products in the Oracle RAC database you have created, then before you attempt to install the products, you must stop all processes running in the Oracle RAC database homes.
You must stop all processes running in the Oracle RAC homes so that Oracle Universal Installer can relink certain executables and libraries. Refer to "Preparing to Upgrade an Existing Oracle RAC Database" for additional information.
There are different configuration processes you must perform when installing and create an Oracle RAC database that uses Direct NFS (dNFS) for the database files.
In a software-only installation you install the Oracle Database software but do not create a database as part of the installation process.
setup.exefrom the software staging location.
Oracle Automatic Storage Management Configuration Assistant (ASMCA) enables you to create an Oracle Automatic Storage Management Cluster File System (Oracle ACFS) mount point which is used in the "common file location" step of Oracle Database Configuration Assistant (DBCA).
asmca.exeto start the ASMCA.
For example, you can specify the following:
This window summarizes the actions performed by ASMCA.
The mount point you just created is displayed on this page.
See Also:Oracle Automatic Storage Management Administrator's Guide for more information about creating an Oracle ACFS file system for database use
Use Oracle Database Configuration Assistant (DBCA) to create an Oracle Real Application Clusters (Oracle RAC) database that uses Direct NFS for datafile storage.
dbca.exeto start the Database Configuration Assistant.
orclrepresents the database SID and
pdb1represents the Pluggable Database (PDB) name:
On each node, create the directory
On the NFS server, create the directory
NET USE * \\filer\vol0\orcl
After you complete this step, both Oracle and the Windows OS can access the location where the database files reside. Oracle is using DNFS, but the Windows OS uses CIFS to access the same location on the NFS server.
SELECT * FROM v$dnfs_servers;
You must manually enable the Direct NFS option after installing the Oracle Database software.
Now you have configured the mount point using Direct NFS, you can remove the Oracle Automatic Storage Management Cluster File System (Oracle ACFS) mount point using Oracle Automatic Storage Management Configuration Assistant (ASMCA).
asmca.exeto start the ASMCA.
C:\oradatamnt), then click Dismount All.
If you have selected to install only the Oracle RAC software on cluster nodes, then you can use Oracle Database Configuration Assistant (DBCA) to configure Oracle RAC One Node.
Oracle Technology Network for more information about Oracle RAC One Node: http://www.oracle.com/technetwork/database/clustering/overview/
You can use DBCA to create an Oracle RAC One Node database that is not a multi-tenant database.
If you select less than two nodes, or create server pools with a cardinality of 2 or more, then DBCA posts a warning message that the configuration you select will not support failover of the Oracle RAC One Node instance.
Note:When you create an administrator-managed Oracle RAC One Node database, while the database is started on only one of the pool of nodes you installed the binaries, all the candidate servers are placed into the Generic server pool. If the servers are not already in Generic or Free, then this may result in stopping resources that run on candidate servers.
Oracle Database Concepts for more information about PDBs
Oracle Real Application Clusters Administration and Deployment Guide for more information about adding services
Deleting an Oracle RAC database using Oracle Database Configuration Assistant (DBCA) involves deleting the database and database objects.
DBCA first deletes the database, and then removes the database's initialization parameter files, instances, Optimal Flexible Architecture (OFA) structure, and the Oracle network configuration for the database.
When you click OK, DBCA continues the operation and deletes all the associated instances for this database. DBCA also removes the parameter files and password files.
At this point, you have accomplished the following:
Deleted the selected Oracle RAC database from the cluster
Deleted the selected Oracle RAC Database Oracle services on Windows-based platforms
Deleted high availability services assigned to the Oracle RAC database
Deleted the Oracle Net configuration for the Oracle RAC database
Deconfigured Oracle Enterprise Manager for the Oracle RAC database
Deleted the OFA directory structure for that Oracle RAC database from the cluster
Deleted the Oracle RAC database data files
During installation, if you select a multitenant container database (CDB), and configure pluggable databases (PDBs), then Oracle recommends that you add services to the PDBs after installation.
PDBs are opened in Read Write mode after failover or relocation only after you have configured the PDBs to have associated services. If you have not associated services to PDBs, then the PDBs remains in
MOUNTED state when the CDB instance restarts.
srvctlcommand syntax, where cdbname is the name of the CDB, service_name is the name of the service, and pdbname is the name of the PDB:
srvctl add service -d cdbname -s service_name -pdb pdbname
After you add services to your PDBs, if you relocate the CDB with which the PDBs are associated, or the CDB fails over, then the PDBs associated with that CDB automatically open in
Read Write state.