Database Reference
In-Depth Information
•
Ability to automatically fail over a database during unplanned circumstances with no admin
intervention
•
Runs over Oracle's Exadata machine
•
Provides better server consolidation solutions where many single-instance databases can
be consolidated into a single server and manage the CPU resources with the use of instance
caging feature
•
Certified compatibility with Oracle VM environments
•
Automated failover of a database when the database or cluster availability becomes unhealthy
•
Less expensive than third-party vendor cold-failover technologies
Oracle RAC One Node comes with an additional cost factor. You will need an additional licensing agreement
with Oracle to be able to use RAC One Node in your production environment and also to access the support for the
product. The license cost is subject to the number of CPUs on the node where RAC One Node is configured; hence,
all the nodes where RAC One Node is configured must be licensed. However, the licensing agreement includes a
ten-day-per-year rule allowing the database to be active without additional cost for ten days on a nonlicensed node
upon database relocation. For more details about licensing and cost, visit the official Oracle website or contact your
local Oracle Support.
Upgrading to 11.2.0.2 or Higher
To upgrade a pre-11.2.0.2 RAC One Node database to 11.2.0.2 or higher, the following steps need to be completed:
1.
Upgrade the existing Grid Infrastructure (GI) using the out-of-place upgrade method,
if not upgraded already
2.
Install 11.2.0.2 or higher RAC or RAC One Node RDBMS binaries
3.
Use Database Upgrade Assistant (DBUA) tool to upgrade the existing RAC One Node
database
■
pre-11.2.0.3 dBUA is not aware of and doesn't sense the RAC One Node database. hence, after upgrading, the
database type will be automatically be set to RAC instead of RACOneNode. therefore, after database upgrade, you need to
explicitly convert the database back to RACOneNode using the
srvctl convert
command.
Note
4.
As a workaround, before upgrading the database, first convert the RAC One Node database
to RAC using the
racone2rac.sh
and then use
DBUA
to upgrade the RAC database. After
completing the upgrade, convert the database back to RACOneNode using the
srvctl
convert
command
Deploying RAC One Node Binaries
Although you can very well make use of the DBCA tool from a typical RAC RDBMS (binaries) home to create a RAC
One Node database, optionally, you can also deploy RAC One Node binaries in a separate Oracle Home on the nodes,
as per your licensing terms. However, before you install RAC One Node software on any node, ensure the Clusterware
software is configured and the cluster stack is up and running on the local node.
