13.1 Base Database Service: DB Systems, RAC, Data Guard, Cloning & Maintenance
Key Takeaways
Oracle Base Database Service offers DB systems on virtual machines as single-node systems or multi-node RAC systems.
Enterprise Edition Extreme Performance is required for multi-node RAC DB systems on Base Database Service.
Oracle has announced the retirement of the VM.Standard.x86 shape, the EE-Extreme Performance edition, and OCPU-metered SKUs for Base Database Service, effective July 31, 2026, for new provisioning.
RAC nodes are placed in different fault domains of one availability domain, while a Data Guard standby can be in another availability domain or region.
Cloning a DB system that has a Data Guard association must start from the primary, and the clone does not copy the Data Guard association.
Where Base Database Service Fits
Oracle Base Database Service runs Oracle AI Database on DB systems that you manage with more control than Autonomous AI Database allows. You get operating system access to the DB system, choose the database version and edition, and decide when to apply updates, while OCI automates provisioning, backups, and patch workflows. It suits applications that need specific database options, custom configurations, or software installed alongside the database.
Base Database Service supports Oracle AI Database 26ai, Oracle Database 21c, and Oracle Database 19c, and it bills OCPU (or ECPU) and storage per second with a one-minute minimum.
DB System Types
Oracle Base Database Service offers DB systems on virtual machines:
| Type | Description | Availability characteristics |
|---|---|---|
| Single-node DB system | One VM running one database instance | A host failure or maintenance requires a restart or a failover to a standby |
| Multi-node RAC DB system | Two or more VMs running Oracle Real Application Clusters on shared storage | Instances are active-active; if one node fails, the others keep serving |
RAC node placement: the nodes of a RAC DB system sit in different fault domains within one availability domain, because RAC needs a low-latency private interconnect. To survive the loss of a whole availability domain or region, add a Data Guard standby in another AD or region.
Editions and the 2026 Retirement Notice
| Edition | Notes |
|---|---|
| Standard Edition | Departmental workloads |
| Enterprise Edition | Core enterprise features, including Data Guard |
| Enterprise Edition – High Performance | Adds options such as Multitenant, Partitioning, Advanced Compression, Advanced Security, and the Diagnostics and Tuning packs |
| Enterprise Edition – Extreme Performance | Adds RAC, Database In-Memory, and Active Data Guard; required for multi-node RAC DB systems |
| Enterprise Edition – Developer | Free database license for development on Ampere A1, single node, LVM storage; no Data Guard and not for production |
Important
Oracle has announced the retirement of the VM.Standard.x86 shape, the Enterprise Edition – Extreme Performance edition, and OCPU-metered SKUs for Base Database Service, effective July 31, 2026. Existing deployments continue to run, but new provisioning and contract renewals are affected. Oracle directs customers to VM.BaseDB.x86 with the ECPU metric, or to Exadata Database Service on Exascale Infrastructure (ExaDB-XS) for workloads that need Extreme Performance features such as RAC.
Storage Management
When you create a DB system you choose how storage is managed:
- Logical Volume Manager (LVM): faster provisioning; used for single-node systems (and the only option for some preview and developer configurations).
- Oracle Automatic Storage Management (ASM): required for RAC, with separate disk groups for data and recovery files.
Block storage for VM DB systems can be scaled up without recreating the system.
Data Guard and Active Data Guard
Oracle Data Guard maintains a synchronized physical standby of a primary database:
- Maximum Availability with synchronous redo transport targets zero data loss for a nearby standby, such as one in another AD.
- Maximum Performance with asynchronous transport suits distant standbys in another region.
- Switchover reverses roles with no data loss for planned events; failover activates the standby during an outage.
Active Data Guard (included with EE-Extreme Performance, or licensed separately) opens the standby read-only while redo is applied, so reports and backups can run on the standby. A standard physical standby cannot be queried while redo apply is running.
Base Database Service manages the Data Guard association through the Console, and Full Stack DR can include these databases as members, verifying during prechecks that the primary and standby are Data Guard peers with the correct roles.
Backups and the Recovery Service
OCI supports automatic daily backups and on-demand full backups. Backup destinations include Object Storage and Autonomous Recovery Service, which Oracle recommends for Oracle-managed automatic backups because it adds incremental-forever backups, validation, and optional real-time protection (Chapter 14). You can create a new DB system from:
- A daily automatic backup or an on-demand full backup.
- The last archived redo log backup, for the most current recovery point.
- A point in time within the automatic backup retention.
- A standalone backup.
Creating and Cloning DB Systems
- Easy Create provisions a DB system with minimal input (database name, edition, administrator credentials, and network) and applies predefined compute, storage, and licensing settings that you review first.
- Cloning a DB system creates a copy of the source system, including its storage configuration and database volumes. The clone can use a different VCN and subnet, a new SSH key, and its own license type. To clone a system that has a Data Guard association, start from the primary; the clone does not copy the Data Guard association. When the source uses customer-managed keys, the clone uses the same key version.
Updates and Maintenance
With Base Database Service, you decide when to apply updates:
- Update the operating system of the DB system periodically, after taking a backup.
- Update the DB system (grid infrastructure) and then the database; Oracle recommends updating the DB system before the database within it.
- Upgrade to newer database versions when needed.
Customers bringing their own licenses must keep a valid support contract and are responsible for applying updates in a timely manner. This responsibility is a key difference from Autonomous AI Database, where Oracle applies patches automatically.
A team needs Oracle RAC for a transactional database on Base Database Service and also wants protection if an entire availability domain fails. Which design is correct?
A RAC DB system whose nodes are spread across all three availability domains of the region
A single-node DB system whose daily backups are copied to another region
Two single-node DB systems in different ADs joined into one RAC cluster over the VCN
A RAC DB system across fault domains in one AD, plus a Data Guard standby in another AD
A reporting team wants to run heavy queries against the disaster recovery copy of a Base Database Service database while it continues to receive and apply changes from the primary. What is required?
Active Data Guard, which opens the standby read-only while redo is applied
A standard physical standby, which can always be queried during redo apply
A snapshot standby, which keeps applying redo while it is open read-write
A clone of the primary refreshed every night from backups
An architect clones a Base Database Service DB system that is the primary in a Data Guard association, to create a test copy. What should the architect expect?
The clone joins the Data Guard configuration automatically as a second standby
The clone comes from the primary and does not include the Data Guard association
The clone must be placed in the same VCN and subnet as the source DB system
Cloning is supported only from the standby DB system of the Data Guard pair
Sections you finish are checked off in the contents.