Oracle Database licensing, the comprehensive pillar.

A comprehensive pillar on Oracle Database licensing, covering editions, metrics, options, packs, virtualization, cloud BYOL and the audit hot spots that move money.

Oracle Database licensing is the deepest commercial software topic most enterprises touch.

The combinations of edition, metric, option and platform create thousands of possible price points for a single deployment.

This pillar lays out the structure that matters, then points to the audit and renewal moments where the price actually gets set.

Editions in plain language

Enterprise Edition

Enterprise Edition is the only Oracle Database edition that supports the full option and pack catalog.

It is the right edition for mission critical workloads, large concurrency and any deployment that needs partitioning, advanced compression or active data guard.

Standard Edition 2

• Hard cap of 16 CPU threads in a single server.
• No options or management packs.
• Two socket cap in a real application clusters configuration.
• Typically the right edition for departmental or mid sized workloads.

Express Edition

Free to use, hard caps on CPU, memory and database size.

Useful for development and small workloads, never for production at scale.

Metrics and how they count

Per processor

Processor licensing counts CPU cores multiplied by the core factor for the chip family.

Used for internet facing workloads, large user populations and any environment where Named User Plus minimums force the price up.

Named User Plus

• Minimum of 25 NUP per processor on Enterprise Edition.
• Counts both human users and non human devices that interact with the database.
• Right for small, defined populations on internal applications.

Options and management packs

Commonly licensed options

Partitioning, Advanced Compression, Active Data Guard, Real Application Clusters and Advanced Security are the most common Enterprise Edition options.

Each option licenses against the same metric as the underlying Database license.

Management packs

• Diagnostics Pack covers AWR, ASH and active session history.
• Tuning Pack covers SQL Tuning Advisor and Real Time SQL Monitoring.
• Lifecycle Management Pack covers configuration, patching and provisioning.
• Data Masking and Subsetting Pack covers test data management.
• All packs require the Diagnostics Pack as a prerequisite in most cases.

Virtualization rules

Hard and soft partitioning

Oracle recognises only specific technologies as hard partitioning.

Soft partitioning, including VMware, must be licensed for every physical core that the database could possibly run on inside the cluster.

VMware in practice

• vSphere clusters with vMotion enabled trigger full cluster counting at audit.
• Dedicated Oracle clusters can contain the count, but the segregation must be physical and documented.
• Storage and DRS rules do not waive the counting requirement.

Options are the audit hot spot. A single touch on Partitioning in a year shows up as use. Disable, document and audit the disable.

Cloud and BYOL

OCI BYOL

OCI BYOL allows existing Database licenses to cover OCI deployments under the published conversion ratio.

OCI Database service includes options and packs that would be separately licensed on premise.

AWS, Azure and Google Cloud

AWS and Azure follow the authorized cloud computing environments policy, with the cloud factor applied to virtual CPU.

Google Cloud follows a separate Oracle partnership pattern for hosted Database services.

• Confirm the cloud policy version in writing.
• Match the deployment shape to a counting rule before deployment.
• Do not assume reserved instance pricing waives the license question.

Audit hot spots in 2026

Option usage in DBA_FEATURE_USAGE_STATISTICS

The LMS audit scripts read DBA_FEATURE_USAGE_STATISTICS. A single touch on Partitioning or Diagnostics in a year shows up as use.

Disable the unused options at the database level. Document the disable. Audit the disable.

Java SE inside the database

• Java SE shipped with the Oracle Database is licensed separately under the Java SE Universal Subscription.
• The Java audit moves on its own cadence and overlaps with Database audits.

Test, development and DR

Test and development deployments need full licensing under standard rules.

Disaster recovery counts under failover rules with a ten day per year limit.

Commercial moves

Renewal preparation

Build the deployment inventory across editions, metrics, options, packs, virtualization platforms and cloud workloads.

Map each line to a contract reference. Lines without a contract reference become priority finds.

Negotiation framing

• Push for a single global agreement where the estate spans entities.
• Negotiate the option list separately from the base license.
• Hold cloud rights as a written reference, not a verbal assurance.
• Set audit notice and data exchange terms at signature.

Suggested reading

• Oracle Database Licensing Guide. Cross vendor reading from the wider library.
• Oracle Database License Cost 2026. Cross vendor reading from the wider library.
• Oracle Audit Response Playbook. Cross vendor reading from the wider library.

What to do next

1. Pull the deployment inventory for every Oracle Database instance across the estate.
2. Run DBA_FEATURE_USAGE_STATISTICS on every production instance and capture the option touch list.
3. Map each option and pack to a contracted entitlement.
4. Score virtualization risk on every VMware cluster that hosts Oracle Database.
5. Confirm cloud BYOL counting for every workload deployed on AWS, Azure, GCP or OCI.
6. Build the renewal model with editions, metrics and options as separate lines.
7. Brief the CIO and CFO before the Oracle account team sees the consolidated estate view.

Frequently asked questions

Can we run Enterprise Edition options without licensing them?

Technically yes. The database does not gate access. The audit catches use through DBA_FEATURE_USAGE_STATISTICS. Disable unused options and document the disable.

Is NUP always cheaper than per processor?

Only when the user population is small enough to stay above the per processor minimum but below the per processor break even point. Build the model both ways.

Does Standard Edition 2 support RAC?

Only under a two socket cap. Larger RAC deployments must run Enterprise Edition with the Real Application Clusters option.

How does Oracle count VMware clusters?

Every physical core in any host that the database could run on across the cluster needs a license. vMotion settings do not waive the count.

Does OCI BYOL include options?

OCI Database services bundle a defined option set by tier. The BYOL credit covers the on premise equivalent license. Read the conversion ratio in writing.

Are test and development environments licensed?

Yes. Test and development require full licensing under standard rules. Only specific failover scenarios get a partial waiver, and only with a ten day per year cap.

How often does Oracle audit Database customers?

Active audits run on a three to four year cadence for most large estates. Soft requests for usage data happen more frequently.

Can we move Oracle Database to Postgres to cut cost?

Sometimes. Migration is a multi year program with workload, feature parity and operational support to design before the license saving lands.