Exadata Database Service Pricing

Exadata Database Service OCPU and the underlying Exadata Infrastructure are separately provisioned. Nondisruptive up-and-down scaling of database core processors along with per-second consumption billing allows you to control costs by aligning consumption to workload needs. The starting configuration for Exadata Cloud Infrastructure and Exadata Cloud@Customer is a quarter rack that includes two Exadata Database Servers and three Exadata Storage Servers. Infrastructure can be expanded by independently scaling compute and storage resources up to a total of 32 database servers and 64 storage servers in a single Exadata cloud environment.

Exadata Database Service OCPUs

Product
Comparison Price
( /vCPU)*
Unit Price
Unit
Exadata Database OCPU – Dedicated Infrastructure
OCPU per hour
Exadata Database OCPU – Dedicated Infrastructure – BYOL
OCPU per hour

Exadata Cloud Infrastructure X9M

Product
Unit Price
Unit
Exadata Cloud Infrastructure - Quarter Rack - X9M

  • Hosted Environment per hour
Exadata Cloud Infrastructure - Database Server - X9M

  • Hosted Environment per hour
Exadata Cloud Infrastructure - Storage Server - X9M

  • Hosted Environment per hour

Exadata Cloud Infrastructure Base System

Product
Unit Price
Unit
Exadata Cloud Infrastructure - Base System

  • Hosted Environment per hour

Exadata Cloud@Customer Infrastructure X10M

Product
Unit Price
Unit
Exadata Cloud@Customer Infrastructure–Quarter Rack - X10M

  • Hosted Environment per month
Exadata Cloud@Customer Infrastructure–Quarter Rack - X10M-XL

  • Hosted Environment per month
Exadata Cloud@Customer - Database Server - X10M

  • Hosted Environment per month
Exadata Cloud@Customer - Database Server - X10M-XL

  • Hosted Environment per month
Exadata Cloud@Customer Storage Server–X10M

  • Hosted Environment per month
Exadata Cloud@Customer - Expansion Rack - X10M

  • Hosted Environment per month

Exadata Database Service OCPUs have a 48-hour minimum commitment and 2 OCPU minimum per database server. If a database instance is terminated less than 48 hours after it’s activated, billing will be for the full 48-hour period. After the initial 48 hours, OCPUs are charged for active hours, and per-second billing applies. For Bring-Your-Own-License (BYOL) details, including eligible Oracle on-premises software licenses and conversion rates (i.e., ratio requirement of software license metric to cloud equivalent metric), refer to the Oracle PaaS and IaaS Universal Credits Service Descriptions document.

*To make it easier to compare pricing across cloud service providers, Oracle web pages show both virtual CPU (vCPU) prices and Oracle CPU (OCPU) prices for products with compute-based pricing. The products themselves, provisioning in the portal, billing, etc., continue to use OCPU units. OCPUs represent physical CPU cores. Most CPU architectures, including x86, execute two threads per physical core, so 1 OCPU is the equivalent of 2 vCPUs for x86-based compute. The per-hour OCPU rate customers are billed at is therefore twice the vCPU price since they receive 2 vCPUs of compute power for each OCPU, unless it’s a sub-core instance such as preemptible instances. Read additional details supporting the difference between OCPU and vCPU pricing.

Exadata Cloud Infrastructure has a 48-hour minimum and no long-term commitment. For pricing information on earlier Exadata Cloud Infrastructure generations, please refer to the Oracle Cloud Price List.

Exadata Cloud@Customer Infrastructure has a four-year subscription term. For pricing information on earlier Exadata Cloud@Customer generations, please refer to the Oracle PaaS and IaaS Global Price List.