|Oracle9i Real Application Clusters Setup and Configuration
Release 2 (9.2)
Part Number A96600-02
This chapter describes using the Database Configuration Assistant (DBCA) to create and delete Oracle Real Application Clusters databases. This chapter also briefly discusses upgrades and multiple Oracle home considerations. The topics in this chapter include:
Oracle9i Real Application Clusters Administration for procedures on using the DBCA to add and delete instances
The primary phases of DBCA processing are:
Oracle Corporation recommends that you use the DBCA to create your database. This is because the DBCA's preconfigured databases optimize your environment to take advantage of Oracle9i features such as the server parameter file and automatic undo management. The DBCA also enables you to create site-specific tablespaces as part of the database creation process. Even if you have datafile requirements that differ from those offered by the DBCA templates, use the DBCA and modify the datafiles afterward. You can also execute user-specified scripts as part of the database creation process.
The DBCA and the Oracle Net Configuration Assistant also configure your Real Application Clusters environment for various Oracle high availability features and cluster administration tools.
To manually create your Real Application Clusters database, refer to Chapter 5. The remainder of this chapter discusses using the DBCA to create a database.
If you did not create a database during installation, then you can create one later using the DBCA in standalone mode. To do this without a cluster file system, you must have configured each raw device as described in Chapter 2. In addition, you must have run the Oracle Net Configuration Assistant to configure your Oracle Net listener file, or you can configure your network manually. The Global Services Daemon (GSD) must also be running on each node in your cluster before you create the database in standalone mode.
If you select a Universal Installer (OUI) database configuration type or one of the DBCA templates that uses preconfigured datafiles and if you do not have a cluster file system, then during database creation the DBCA first verifies that you created the raw devices for each tablespace. If you have not properly set up the raw devices, then you must replace the default datafiles with raw device names on the Storage page to continue database creation.
To start the DBCA, on one of the nodes:
To use the DBCA to create a Real Application Clusters database that uses datafiles from a CFS partition launch the DBCA as follows:
On UNIX, for example, create a directory on the CFS partition called
oradata, change its ownership to
oracle user, and execute the following command:
On Windows, for example, create a directory on the CFS partition called
oradata on the CFS partition, where the CFS partition drive name is
p:, then execute the DBCA from the command prompt using the following syntax:
The following section describes how to use the DBCA to create a database for Real Application Clusters. The first page the DBCA displays is the Database Configuration Assistant Welcome page for Real Application Clusters shown in Figure 4-1. The DBCA only displays this page when it detects that your Cluster Manager (CM) software is running.
If the DBCA does not display the Real Application Clusters Welcome page with the Oracle cluster database option, then perform clusterware diagnostics as shown in the bulleted items in Step 6.
If the DBCA Welcome page for Real Application Clusters does not display, then it means that the DBCA was unable to:
To create a Real Application Clusters database:
You cannot successfully click Back after clicking Next. This prevents configuration problems that result from creating databases for both single-instance and cluster database environments during the same DBCA session.
After you click Next, the DBCA displays the Operations page shown in Figure 4-2.
The DBCA only enables Instance Management if there is at least one Real Application Clusters database configured on your cluster.
The Node Selection page shows the nodes that the DBCA detects in your cluster.
If the GSD is not running on any of the nodes, then the DBCA displays a dialog explaining how to start the daemon using the
After you click Next, the DBCA displays the Database Templates page shown in Figure 4-4.
The templates on this page include the Transaction Processing, General Purpose, and Data Warehouse preconfigured templates. These templates include datafiles and specially configured options for each environment. However, the New Database template does not include datafiles or the specially configured options.
After you click Next, the DBCA displays the Database Identification page shown in Figure 4-5.
After you click Next, if you selected the New Database template, then the DBCA displays the Database Features page shown in Figure 4-6. If you selected one of the other preconfigured database options, then after you click Next the DBCA displays the Initialization Parameters page shown in Figure 4-8.
If you select Create server parameter file (spfile), then you may need to modify the location for the server parameter file depending on the type of file system you use as described for the following conditions:
The DBCA does not enable you to specify archive log destinations on a per-instance basis. To set the archive log destination for each instance follow the procedures under the heading "Setting the Log Mode".
Instance-specific parameter settings for your Real Application Clusters database appear at the bottom of this dialog. The sid prefixes for these entries appear in the left-hand column.
The DBCA only places a parameter entry into the server parameter file if the entry displays a check mark in the Included (Y/N) column on the All Initialization Parameters dialog. Also note the following about the All Initialization Parameters dialog:
Use the Database Storage page to enter file names for each tablespace such as
INDX, and so on. The Storage page displays these file names in the Datafiles folder.
Platform-specific issues for entering file names in the Database Storage page are:
DBCA_RAW_CONFIGenvironment variable, then the 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.
If you select a template that includes datafiles, then the Storage page does not display tablespace information. Instead, the Storage page displays default datafile file names that you must replace with raw device file names. If you are creating a database with a preconfigured database template, then the Storage page does not enable you to change tablespace sizes.
After you click Finish, the DBCA displays a Summary dialog similar to the dialog in Figure 4-12.
After you click OK, the DBCA displays a password page similar to the page in Figure 4-13.
Use the password page to override the default password settings for the
SYSTEM user accounts.
If you create a database using the DBCA in silent mode and use the
true parameter, then the DBCA displays the password page and requires that you change the default passwords for these user accounts. You can later activate locked accounts manually by using, for example,
The DBCA password page also provides access to the Password Management page that enables you to selectively unlock and specify new passwords for other Oracle9i default user accounts.
After you complete this step, at this point in the database creation process you have:
This section explains how to delete a Real Application Clusters database with the DBCA. Using the DBCA to delete a database 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 the DBCA:
dbcacommand from the
The DBCA Welcome page appears as shown earlier in this chapter in Figure 4-1.
After you click Next, The DBCA displays the Operations page in Figure 4-14.
After you click Finish, the DBCA displays a Database Deletion Summary dialog showing the database name and associated instances that the DBCA is going to delete. This Summary dialog, which is similar to the dialog in Figure 4-16, also describes the node on which each instance resides.
When you click OK, the DBCA continues the operation and deletes all of the associated instances for this database. The DBCA also removes the parameter files, password files, OracleServicesid services, and oratab entries.
At this point, you have accomplished the following:
If the Oracle Universal Installer (OUI) detects an earlier version of Oracle, then the Installer prompts you to upgrade to Oracle9i release 2 (9.2). Select the upgrade option to upgrade to Oracle9i release 2 (9.2).
The Oracle9i Database Migration guide for information about using the Database Upgrade Assistant
The compatible co-existence of different versions of Oracle database software depends on your operating system platform.
For UNIX operating systems, whether different versions of Oracle can exist on the same cluster is platform-dependent. Refer to your platform-specific Oracle documentation for more information about version co-existence.
For Windows NT and Windows 2000 platforms, as long as your Oracle database software versions are greater than 8.1, they can co-exist on the same cluster when you install them in different locations with different Registry keys. This means that you cannot have different versions of Oracle with version numbers that are older than release 8.1 on the same cluster. For example, a release 1 (9.0.1) Real Application Clusters database and a release 8.0 Oracle Parallel Server database cannot co-exist on the same cluster.
For Windows NT and Windows 2000, operating system-dependent (OSD) clusterware from Oracle9i release 2 (9.2) can co-exist with previous versions. However, only one version can be active at a time. In addition, an earlier version of the OSD cannot support a later version of the database. Only Oracle9i release 2 (9.2) is backward compatible with Oracle9i release 1 (9.2).
The term rolling upgrades refers to upgrading different databases or different instances of the same database in Oracle9i Real Application Clusters one at a time, without stopping the database. Release 2 (9.2) of Oracle9i Real Application Clusters does not support rolling upgrades.
Oracle9i Real Application Clusters on UNIX, Windows NT, and Windows 2000 platforms supports multiple Oracle homes, just as the single-instance Oracle9i Enterprise Edition database does. The multiple homes feature enables you to install one or more releases on the same machine in multiple Oracle home directories.