This is an excerpt from the bestselling book
Oracle Grid & Real Application Clusters. To get immediate
access to the code depot of working RAC scripts, buy it
directly from the publisher and save more than 30%.
To create the required services
on the DBCA 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 then click Add to add
services to the database. Enter a service name in the Add a Service
dialog and click OK.
The service name will appear
under the global database name. Select the service name and the DBCA
will display the service preferences for the service on the
right-hand side of the DBCA Database Services page. Change the
instance preference (preferred or available) and total application
failover (TAF) policies for the service as needed. Repeat this
procedure for each service and when configuration of the services
for the database is complete, click Next. The DBCA will now display
the Initialization Parameters page.
Now, select the File Locations
tab on the Initialization Parameters page.
If Create server parameter file
(spfile)is selected, then it may be necessary to modify the location
for the server parameter file depending on the type of file system
used as described for the following conditions:
* If using a cluster file
system, or if a single-node RAC environment exists, then the server
parameter file can be placed on the file system.
* If not using a cluster file
system and you not creating a single-node RAC database, then a raw
device name for the location of the server parameter file must be
entered in the Server Parameter Filename field in the center of the
Initialization Parameters page.
Next, select the Archive tab on
the Initialization Parameters page to see or check the archive log
destination settings.
Now, click the Advanced
Parameters tab and the DBCA will display the All Initialization
Parameters dialog. Carefully review the parameter settings displayed
in this dialog because the DBCA will configure these settings in the
server parameter file. Instance-specific parameter settings for the
RAC database appear at the bottom of this dialog. The sid prefixes
for these entries will appear in the left-hand column.
To review the instance-specific
parameter settings, scroll downward using the scroll bar on the
right-hand side of the dialog box.
Note: Using the DBCA you cannot
specify archive log destinations for each instance in the cluster.
Use the check box in the
Included (Y/N) column of the dialog to indicate whether the DBCA
should place the parameter setting in the server parameter file. The
DBCA will only place 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:
* The SID in the Instance column
cannot be modified.
* Although the self-tuning
parameters can be altered with this dialog, setting these parameters
to inappropriate values will disable the Oracle self-tuning
features.
* Instance-specific values for
global parameters cannot be specified with the DBCA.
Once all entries are complete in
the All Initialization Parameters dialog, click on Close. Make sure
that entries for the File Locations tab and the other tabs are
correct for the RAC database, and then click Next. The DBCA will
display the Database Storage page.
If preconfigured database
template was selected, such as the General Purpose template, then
the DBCA will display 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. However, if the
New Database template is selected, the template is without
datafiles, and the 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 and click the tablespace.
The tablespace property dialog
appears on the right-hand side. Make necessary changes and click OK.
Platform-specific topics for entering file names in the Database
Storage page are:
* For UNIX-based platforms, if
the dbca_raw_config environment variable is not set, then the DBCA
displays default datafile names. Override values must be entered for
these names to provide raw device names for each control file,
datafile, and redo log group file.
* For Windows-based platforms,
if the default symbolic links exist, then the DBCA replaces the
default datafiles with these symbolic link names and displays them
in the Storage page. If the symbolic links do not exist, then the
DBCA displays the default file system datafile file names on the
Storage page. In this case, replace the default datafile file names
with the symbolic link names.
After completing the entries on
the Database Storage page, click Next, and the DBCA displays the
Creation Options page. Select one of the following database options
and then click Finish.
* Create Database: This option
creates the database.
* Save as a Database Template ?
This option creates a template that records the database structure,
including the supplied inputs, initialization parameters, and so on.
This template can be used later to create a database.
* Generate Database Creation
Scripts ? This option generates database creation scripts.
The DBCA only displays the last
option if the New Database template was selected. After clicking
Finish, the DBCA will display a Summary dialog. Review the Summary
dialog information and click OK. To cancel database creation at this
point, click on Cancel.
After completion of above steps,
the DBCA:
* Creates the RAC data
dictionary views
* Creates an operative RAC
database
* Configures the network for the
cluster database
* Starts the services if on a
Windows-based platform
* Starts the listeners and
database instances and then starts the high availability services
Now a new database exists. It
can be accessed via Oracle SQL*Plus or other applications designed
to work with an Oracle RAC database. The above method is a generic
procedure that is applicable irrespective of the cluster platform.