Creating an Oracle RAC One Node Database

You can create Oracle RAC One Node databases by using Fleet Patching and Provisioning or the Oracle DBCA, as with any other Oracle AI Database (manually created scripts are also a valid alternative).

You can create an Oracle RAC One Node database using Fleet Patching and Provisioning and the rhpctl add database command with the -dbtype RACONENODE parameter. You can also include an Oracle RAC One Node database using the rhpctl add workingcopy command.

Oracle RAC One Node databases may also be the result of a conversion from either a single-instance Oracle AI Database 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.

Note:

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 -dbtype  RACONENODE [-server server_list]
  [-instance instance_name] [-timeout timeout]

Use the -server option and the -instance option when adding an administrator-managed Oracle RAC One Node database.

Note:

The policy-managed database deployment option is desupported in Oracle AI Database 26ai.

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 Oracle RAC One Node database, service registration is performed as with any other Oracle RAC database.

Note:

When adding an Oracle RAC One Node database, you can optionally supply an instance prefix with the -instance instance_name parameter of the srvctl add database command. The name of the instance will then be prefix_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 prefix_2 during an online database relocation and reverts back to prefix_1 during a subsequent online database relocation. The same instance name is used on failover.