OCI Database Options Licensing: Avoiding Silent Shortfalls
Oracle database options and management packs are licensed separately from the base database on OCI, just as they are on premise. Under BYOL you must own each option you enable; under License Included the option is bundled into higher tier services. Enabling an option you have not licensed is the most common OCI audit finding.
Why options are licensed separately
Oracle Database options such as Partitioning, Real Application Clusters, Advanced Security, and Active Data Guard, together with the management packs like Diagnostics and Tuning, are separately licensed products that sit on top of the base Enterprise Edition database. This is true on premise and it remains true on OCI. The base database licence, whether owned or bundled, never includes the options; each one is a discrete entitlement that must be held or paid for in its own right. The full on premise picture is set out in database options and packs.
In the cloud this principle survives but the enforcement does not. On premise, enabling an option you have not licensed at least leaves a trail in your own systems. On OCI the option can be switched on with a single parameter, and nothing stops you, so a base database can silently acquire a chargeable option that nobody bought. The gap accumulates from the moment the option is enabled, which is why options are the sharpest edge in the Oracle OCI licensing model.
Options under BYOL
Under BYOL, every option you enable on an OCI database must be matched by an owned option licence, counted on the same metric as the base database. If you carry sixteen Enterprise Edition processor licences and enable Partitioning across all sixteen OCPUs, you must also own sixteen Partitioning processor licences. The conversion follows the same two vCPU rule described in OCPU versus vCPU, so the option count tracks the base count exactly.
| Option or pack | Separately licensed? | Frequent OCI trap |
|---|---|---|
| Partitioning | Yes | Enabled by default in many schemas |
| Diagnostics Pack | Yes | AWR and ADDM access counts as use |
| Tuning Pack | Yes | SQL Tuning Advisor triggers it |
| Advanced Security | Yes | TDE often switched on for compliance |
| Real Application Clusters | Yes | Assumed bundled, rarely is under BYOL |
The most insidious finding is the management pack. Simply querying the Automatic Workload Repository or running the SQL Tuning Advisor constitutes use of the Diagnostics or Tuning Pack, and OCI does not block the query. A DBA investigating performance can incur a pack liability without ever intending to licence one. The defensive control is to disable unlicensed packs at the database level so the option cannot be touched, not merely to instruct staff not to use it.
The licence metric for an option always mirrors the base database metric, which has a subtle consequence under Named User Plus. If the base database is licensed by NUP rather than processor, the option must also be NUP and must satisfy the same per processor user minimums. Buyers who carry a NUP base into the cloud sometimes licence options by processor by mistake, creating both an over spend on metric and a potential minimums shortfall. Matching the option metric exactly to the base is a small check that avoids both errors.
Options under License Included
Under License Included, options are handled by service tier rather than by separate purchase. OCI bundles options into the higher database editions: the Enterprise Edition High Performance tier includes a defined set of options and packs, and the Enterprise Edition Extreme Performance tier includes the full set plus Real Application Clusters and Active Data Guard. You pay for the tier, and the options inside it are covered for as long as you run that tier.
This bundling cuts both ways. It removes the risk of an unlicensed option, because the tier covers everything it contains, but it can also force you to pay for a high tier to obtain one option you need, carrying a dozen you do not. A buyer choosing License Included should map the specific options each workload requires to the cheapest tier that contains them, rather than defaulting to the top tier for safety. The tier to shape relationship is covered in OCI compute licensing.
Which options are included in each tier?
The tier mapping is the single most useful thing to know before choosing License Included. Standard Edition 2 on OCI includes none of the Enterprise options. Enterprise Edition base includes the database with no options. High Performance adds the common options most workloads need, including Partitioning, Advanced Security, Advanced Compression, the Diagnostics and Tuning Packs, and several others. Extreme Performance adds Real Application Clusters, Active Data Guard, In Memory, and the remaining options aimed at mission critical estates.
The practical decision is whether your workload needs anything in Extreme Performance. If it needs only Partitioning and the management packs, High Performance is the correct and cheaper choice. If it needs RAC or Active Data Guard, Extreme Performance is unavoidable. Mapping the requirement to the minimum sufficient tier is exactly the analysis that prevents over paying, and it is the same logic applied to Exadata Cloud Service, which bundles the full option set by default.
The triggers that enable an option
Oracle determines option usage by inspecting feature usage data, and the triggers are often subtler than a deliberate configuration. Creating a partitioned table enables Partitioning. Setting up an Oracle Managed Standby in read mode enables Active Data Guard. Encrypting a tablespace with Transparent Data Encryption enables Advanced Security. Each is a single action, often taken by a developer or DBA solving a local problem, and each leaves a feature usage record that an audit reads as licensable use.
The control is feature usage monitoring run by the customer, not just by Oracle. Querying DBA_FEATURE_USAGE_STATISTICS on each OCI database reveals exactly which options have been touched, and comparing that list to held entitlement surfaces shortfalls before Oracle does. Running this query as a standing monthly control turns option compliance from a reactive audit risk into a governed position, the same discipline the audit defence practice installs.
A practical control is to capture a baseline of feature usage immediately after each database is provisioned and again after any major application change, then diff the two. Options rarely appear by accident in a static database; they appear when a developer ships a feature, a DBA enables a diagnostic, or a security team mandates encryption. Tying the feature usage check to those change events catches the option at the moment it is enabled, when disabling or licensing it is a deliberate choice rather than a buried surprise.
The audit exposure from options
Options are the highest value, lowest visibility audit finding on OCI. A single unlicensed option enabled across a large database can carry a list price liability comparable to the base database itself, because options are priced as a percentage of the Enterprise Edition licence. Partitioning at fifteen thousand per processor, multiplied across sixteen OCPUs, is a quarter of a million dollars in list exposure from one parameter, and it accrues for every month the option was active.
Because OCI does not enforce option entitlement at provisioning, the gap is invisible until Oracle requests feature usage data, at which point months of accrual are valued at once. The only defence is prevention: disable unlicensed options at the database level, monitor feature usage monthly, and reconcile against entitlement. A shortfall caught internally is corrected for the cost of the licence; one found in an audit is valued with back support and negotiating leverage on Oracle's side. The exposure is quantified in the cloud and OCI practice.
The negotiating dimension matters too. When Oracle raises an options finding, the figure is anchored at list price across the full accrual period, and the customer's only leverage is the quality of its own records. A customer who can show that the option was enabled on a known date, used briefly, and then disabled is in a far stronger position than one who cannot say when use began. The feature usage history is therefore not just a compliance artefact; it is the evidence base for any negotiation that follows a finding.
How to govern options on OCI
Governing options comes down to four standing controls. Disable every option and pack you have not licensed at the database parameter level so it cannot be enabled accidentally. Monitor feature usage statistics monthly on every OCI database and reconcile to entitlement. Choose License Included tiers by mapping required options to the minimum sufficient tier rather than the top one. And record the option position in the same governance file as the base licence reconciliation.
These controls cost almost nothing and remove the most expensive surprise in cloud licensing. The buyer who treats options as a first class part of the licence position, rather than an afterthought to the base database, is the one who never receives an options finding. That posture is consistent across the whole OCI licensing cluster.
The buyer side view
Treat options and packs as separately licensed on OCI exactly as on premise, because they are. Under BYOL, own every option you enable and disable the ones you do not. Under License Included, map your required options to the cheapest tier that contains them rather than defaulting to the top. Monitor feature usage monthly, because a single parameter can create a six figure liability that accrues silently. Govern options as a first class part of the licence position. To run a feature usage reconciliation across your OCI estate, request a consultation.
Common questions.
Are database options licensed separately on OCI?
Yes. Options such as Partitioning, RAC, and Advanced Security, and management packs like Diagnostics and Tuning, are separately licensed on OCI just as on premise. The base database never includes them, so each must be owned under BYOL or bundled in a License Included tier.
How do I license options under BYOL on OCI?
Under BYOL you must own an option licence for every OCPU on which the option is enabled, counted on the same metric as the base database. Enabling Partitioning across sixteen OCPUs requires sixteen Partitioning processor licences in addition to the base.
Which options are included in OCI License Included tiers?
Enterprise Edition base includes no options. High Performance adds common options including Partitioning, Advanced Security, and the Diagnostics and Tuning Packs. Extreme Performance adds Real Application Clusters, Active Data Guard, and In Memory among others.
What triggers an option to count as used?
A single action triggers use: creating a partitioned table enables Partitioning, encrypting a tablespace enables Advanced Security, and querying the AWR enables the Diagnostics Pack. Oracle reads the feature usage record as licensable use regardless of intent.
How do I check which options are in use?
Query DBA_FEATURE_USAGE_STATISTICS on each OCI database to see which options and packs have been touched, then compare to held entitlement. Running this monthly surfaces shortfalls before Oracle requests the data in an audit.
Why are options the biggest OCI audit risk?
Options are priced as a percentage of the Enterprise Edition licence, so one unlicensed option across a large database can rival the base licence in value. OCI does not enforce option entitlement, so the gap accrues silently until an audit values months of use at once.