Oracle Database Cloud Service (DBCS) — now rebranded as Oracle Base Database Service on OCI — is Oracle's managed database service for enterprises running Oracle Database in Oracle Cloud Infrastructure. The billing model, BYOL rules, high availability licensing, and Database option availability differ significantly from on-premise licensing, and the differences consistently produce surprise costs for enterprises that assume cloud database licensing works the same way as their on-premise perpetual licenses. Former Oracle insiders map every cost component, every BYOL trap, and how to negotiate a cloud database deployment that doesn't cost twice what you expected.
Oracle Database Cloud Service (DBCS) was Oracle's original managed database offering on OCI, launched in 2014. In 2021, Oracle rebranded the service as Oracle Base Database Service (BaseDB) as part of a broader OCI product naming rationalization. The underlying service is the same — a managed Oracle Database deployment on OCI VM or Bare Metal compute, with Oracle managing the infrastructure and the customer managing the database itself. The rebrand does not change the licensing rules, pricing structure, or BYOL terms.
Base Database Service supports Oracle Database versions from 11g Release 2 through the current 23ai, across Standard Edition 2 and Enterprise Edition configurations. Oracle manages patching, backup, and infrastructure provisioning; the customer retains control over schema, data, application code, and database configuration. This model sits between fully managed Autonomous Database (where Oracle manages everything) and self-managed Database on OCI compute (where the customer manages everything).
Understanding which OCI Database service applies to your use case is the first licensing decision. Base Database Service is appropriate for enterprises that need full Oracle Database feature access, control over database configuration, and compatibility with existing on-premise application architectures. Autonomous Database is appropriate for workloads where Oracle-managed operation is acceptable and the additional cost of Autonomous can be offset by reduced DBA overhead. Each service has its own pricing model and its own interaction with BYOL.
Our Oracle Cloud Licensing Guide provides a complete overview of Oracle's cloud database services — Base Database Service, Autonomous Database, Exadata Cloud Service, and Exadata Cloud@Customer — with their respective pricing structures and BYOL rules.
Oracle Cloud Infrastructure uses its own compute unit — the OCPU (Oracle CPU) — as the fundamental billing metric for cloud services. One OCPU is equivalent to two physical processor cores (or one physical processor core with hyper-threading enabled). This is Oracle's definition and it differs from how AWS, Azure, and GCP measure and price compute — a difference that has significant cost implications when you are evaluating OCI pricing against competitor cloud database services.
For Oracle Base Database Service, pricing is charged per OCPU per hour, with different rates depending on Database edition (Standard Edition 2 or Enterprise Edition) and whether you are using the license-included pricing or Bring Your Own License (BYOL) pricing. The license-included price covers both the OCI infrastructure cost and the Oracle Database software license cost in a single hourly rate. The BYOL price covers only the OCI infrastructure cost — the assumption is that you are applying your existing on-premise perpetual Oracle Database licenses to the cloud instance.
| Service Configuration | OCPU/Hour (approx.) | What's Included |
|---|---|---|
| Base DB: EE — License Included | $0.96–$1.20/OCPU/hr | OCI compute + Oracle Database EE license + support |
| Base DB: EE — BYOL | $0.26–$0.32/OCPU/hr | OCI compute only — customer must provide EE license |
| Base DB: SE2 — License Included | $0.45–$0.55/OCPU/hr | OCI compute + Oracle Database SE2 license + support |
| Base DB: SE2 — BYOL | $0.08–$0.12/OCPU/hr | OCI compute only — customer must provide SE2 license |
| Prices are approximate and vary by OCI region and shape type. Always verify current OCI pricing calculator for actual regional rates. | ||
The cost difference between license-included and BYOL is substantial — approximately 70% for Enterprise Edition. For organizations with existing perpetual Oracle Database EE licenses and active Oracle Support, BYOL is the correct model: you pay only for the OCI infrastructure while applying your existing license entitlement. However, applying BYOL correctly requires careful calculation and documentation to avoid both under-counting (compliance risk) and over-counting (cost waste).
Oracle's Bring Your Own License policy for OCI Base Database Service allows enterprises with existing perpetual Oracle Database licenses and active Oracle Support to apply those licenses to OCI cloud deployments. The BYOL calculation follows Oracle's standard Processor (CPU) metric, with an important OCI-specific conversion: one on-premise Processor License covers two OCPUs in OCI (because one OCPU = two physical processor cores, and Oracle's Processor metric = two physical cores for most modern processors with a Core Factor of 0.5).
For practical planning: if you hold four Processor Licenses for Oracle Database Enterprise Edition on-premise, those four licenses cover eight OCPUs in OCI Base Database Service under BYOL. An OCI VM.Standard.E4.Flex shape configured with 8 OCPUs would be fully covered by those four Processor Licenses, and you would pay only the BYOL rate (infrastructure only) rather than the license-included rate.
The BYOL rules carry several critical constraints that enterprises routinely overlook. First, on-premise licenses used for BYOL must remain on active Oracle Support — you cannot use licenses that have lapsed support to satisfy OCI BYOL requirements. Second, the licenses used for BYOL must be unused in production elsewhere: you cannot "stretch" on-premise licenses to cover both your on-premise database deployment and an OCI BYOL deployment simultaneously. If you are migrating a workload from on-premise to OCI, the BYOL calculation assumes you will decommission the on-premise deployment and release those licenses for cloud use.
BYOL Compliance Warning: Oracle's BYOL policy requires that on-premise licenses used for OCI BYOL are not simultaneously deployed on-premise. Dual-running on-premise and OCI environments — typical during migration transition periods — requires either license-included OCI pricing for the cloud instance, or a separate "lift-and-shift" contractual arrangement with Oracle that permits temporary dual use. Running BYOL on OCI while maintaining the same license in production on-premise is a compliance violation.
We calculate your BYOL entitlement, identify the optimal OCI shape configuration, model license-included vs BYOL economics, and ensure your transition plan doesn't create dual-use compliance exposure.
Oracle Base Database Service supports both Standard Edition 2 and Enterprise Edition, with important limitations on which Database options are available in each edition and in each OCI deployment model. Understanding these limitations before designing your cloud database architecture prevents both compliance gaps and expensive surprises when features you expected to be available are not.
Oracle Database SE2 in OCI has the same feature limitations as on-premise SE2: it supports a maximum of 16 OCPUs per instance (equivalent to 8 Processor Licenses on-premise), it does not support Oracle RAC, and it does not include Enterprise Edition options such as Advanced Security, In-Memory, Diagnostics Pack, or Tuning Pack. SE2 in OCI is the correct choice for departmental databases, development environments, and workloads with moderate data volumes and user counts that do not require EE features.
Oracle Database EE in OCI supports all Enterprise Edition options, but with a critical caveat: Database options such as Diagnostics Pack, Tuning Pack, Advanced Security, Partitioning, and In-Memory carry separate license costs in addition to the base EE license. In the license-included OCI pricing model, Oracle typically includes the base EE license but not the options — if you enable the Diagnostics Pack (including its Cloud Control metrics) in your OCI database instance, you are incurring an obligation for a Diagnostics Pack license, in addition to the EE license-included rate you are already paying.
The same "accidentally enabled options" risk that creates massive audit exposure in on-premise Oracle Database environments applies in OCI. The Oracle Diagnostics Pack Licensing guide explains how to prevent accidental option enablement in any Oracle Database deployment, including cloud instances.
Oracle Base Database Service supports two high availability options: a single-instance deployment with automated backup and recovery, and a Data Guard configuration with a primary and standby database. The Data Guard option creates significant license cost implications that are frequently overlooked in cloud database architecture planning.
Oracle's standard license terms permit a cold standby database (inactive standby used only for failover) at no additional license cost. However, Oracle Active Data Guard — which allows the standby database to be open for read queries while the primary is active — requires a separate Active Data Guard license for every OCPU of the standby database. In a Base Database Service Data Guard configuration with an 8-OCPU primary and an 8-OCPU standby, enabling Active Data Guard doubles the license requirement for the Active Data Guard option.
Many enterprises deploy OCI Base Database Service with Data Guard and enable Active Data Guard read access — either deliberately for reporting queries or inadvertently because OCI's default recommended configuration includes Active Data Guard. Without an Active Data Guard license to cover the standby OCPUs, this creates an immediate compliance exposure. The Oracle Data Guard Licensing guide provides complete detail on the standby database rules for both on-premise and OCI deployments.
Oracle Base Database Service is available on two infrastructure types: VM shapes (virtual machine deployments on shared physical hardware) and Bare Metal shapes (dedicated physical servers with no virtualisation layer). The licensing implications differ significantly between the two.
VM shapes in OCI are treated as hard partitioned from a licensing perspective — Oracle designed OCI's VM architecture to comply with their own licensing policies. When you deploy Oracle Database on a VM shape with a specified OCPU count, Oracle licenses only those OCPUs. You do not need to license the full physical host. This is the key differentiator from VMware on-premise deployments, where Oracle's policy requires licensing all physical cores on the VMware cluster.
Bare Metal shapes do not use virtualisation — they provide dedicated physical servers. For Bare Metal Oracle Database deployments in OCI, you are typically required to license all OCPUs on the physical Bare Metal server. For example, a BM.DenseIO.E4.128 Bare Metal shape with 128 OCPUs requires licensing all 128 OCPUs under BYOL — equivalent to 64 on-premise Processor Licenses. This is rarely the most cost-effective choice for standard database workloads, but may be appropriate for high-performance or Exadata-comparable requirements.
For enterprises evaluating OCI vs on-premise costs, the VM shape flexibility is one of OCI's genuine advantages: you can provision exactly the OCPU count required, and scale up or down at the shape level, without the on-premise burden of licensing entire physical servers. The Oracle Cloud Advisory service models these cost differences as part of every cloud migration assessment.
The most frequently encountered cost traps in Oracle Database cloud deployments follow predictable patterns. Understanding these traps before you provision your OCI database architecture prevents the surprise costs that consistently emerge during or after cloud migration projects.
The first trap is license-included pricing without modelling the total cost over three to five years. At $0.96 per OCPU per hour for Enterprise Edition license-included, a 16-OCPU OCI database deployment costs approximately $134,000 per year — comparable to the Oracle Support cost on perpetual licenses for the same compute capacity. But the license-included rate locks you into OCI and does not build equity in perpetual license assets. Enterprises with existing EE licenses almost always find BYOL significantly cheaper.
The second trap is BYOL dual-use during migration. Organizations running Oracle Database on-premise while standing up the OCI environment for testing and migration validation often run BYOL on OCI using the same licenses that are still in production on-premise. This creates a compliance gap. The solution is either to use license-included pricing for the OCI test environment, to formally decommission the on-premise database before running BYOL in OCI production, or to negotiate a contractual "cloud migration" accommodation with Oracle that permits temporary dual use.
The third trap is Oracle Support Rewards dilution. Oracle's Support Rewards program allows OCI consumption credits to offset Oracle Support costs — up to 33% of the annual support invoice per year. If your organization is paying Oracle Support on on-premise Database licenses and also running OCI workloads, the Support Rewards program can be a genuine cost saving. However, Support Rewards requires careful tracking of OCI consumption against eligible support contracts, and Oracle's program administrators have strict requirements for which OCI services generate eligible credits.
The highest-return optimization for most enterprises planning OCI database deployments is a structured BYOL assessment before migration. Identifying the full extent of your existing Oracle Database EE perpetual licenses, validating they are on active Oracle Support, and calculating the exact OCPU coverage they provide in OCI allows you to maximize BYOL utilization and minimize license-included costs.
BYOL maximisation requires decommissioning on-premise databases in parallel with OCI provisioning — a migration approach that creates compliance pressure but reduces the total cost significantly. Our Oracle Cloud & OCI Advisory service designs migration sequences that maximize BYOL utilization while managing the compliance transition risk.
For enterprises committing to significant OCI consumption, Oracle Universal Credits provide volume discounts and flexibility across all OCI services. A Universal Credits commitment that covers both OCI compute (for your databases) and additional OCI services (for your application tier, storage, and networking) can achieve 15–25% discounts over pay-as-you-go rates, with the Oracle Support Rewards program reducing the annual Database support bill by up to 33% when OCI consumption is tracked correctly.
The Oracle OCI vs AWS Decision Framework white paper provides a complete cost comparison methodology for enterprise database workloads — including the full BYOL economics, infrastructure cost differences, and the five-year total cost of ownership comparison that should inform every cloud database platform decision.
Download our comprehensive cloud migration guide — including BYOL calculation worksheets, OCI Base Database Service cost modelling templates, Data Guard licensing rules, and a decision framework for license-included vs BYOL for every Oracle Database workload type.
Download Free Guide →Weekly intelligence on Oracle cloud licensing, BYOL strategy, and OCI cost optimization — written by former Oracle insiders who know what Oracle's sales team doesn't tell you.