You can create Oracle RAC One Node databases by using the Database Configuration Assistant (DBCA), as with any other Oracle database (manually created scripts are also a valid alternative). Oracle RAC One Node databases may also be the result of a conversion from either a single-instance Oracle database (using
rconfig, for example) or an Oracle RAC database. Typically, Oracle-provided tools register the Oracle RAC One Node database with Oracle Clusterware. Depending on your configuration, automatic registration of an Oracle RAC One Node database with Oracle Clusterware may not have happened. If this is the case, then follow the steps in this section to register the Oracle RAC One Node database with Oracle Clusterware.
Oracle recommends that you manage Oracle RAC One Node databases with Server Control Utility (SRVCTL). You can only perform certain operations (such as Online Database Relocation) using SRVCTL.
If your Oracle RAC One Node database did not register automatically with Oracle Clusterware, then use the
srvctl add database command to add an Oracle RAC One Node database to your cluster. For example:
srvctl add database -c RACONENODE [-e server_list] [-i instance_name] [-w timeout]
-e option and the
-i option when adding an administrator-managed Oracle RAC One Node database.
"srvctl add database" for usage information
"Using DBCA in Interactive Mode to Add Database Instances to Target Nodes" for more information about adding an Oracle RAC One Node database
For Oracle RAC One Node databases, you must configure at least one dynamic database service (in addition to and opposed to the default database service). When using an administrator-managed Oracle RAC One Node database, service registration is performed as with any other Oracle RAC database. When you add services to a policy-managed Oracle RAC One Node database, SRVCTL does not accept any placement information, but instead configures those services using the value of the
When adding an administrator-managed Oracle RAC One Node database, you can optionally supply an instance prefix with the
instance_name option of the
srvctl add database command. The name of the instance will then be
_1. If you do not specify an instance prefix, then the first 12 characters of the unique name of the database becomes the prefix. The instance name changes to
_2 during an online database relocation and reverts back to
_1 during a subsequent online database relocation. The same instance name is used on failover.