Get Oracle Licensing Insights Delivered
Join enterprise IT leaders receiving our monthly advisory on Oracle licensing strategy, audit preparation, and cost optimisation tactics.
CIO Playbook · Oracle Database Licensing · July 2025
01 Background & Licensing Landscape
Oracle Database Editions
Standard Edition 2
Lower-cost edition for smaller/mid-sized deployments. Licensed per processor socket (not per core). Maximum 2 CPU sockets per server (up to 16 threads per instance). Approximately $17,500 per socket list price. No RAC (19c+), no optional packs, limited parallel query. Ideal for departmental apps, legacy systems, dev/test environments.
Enterprise Edition
Flagship edition for mission-critical, large-scale systems. Licensed per CPU core (multiplied by Core Factor table). Unlimited cores and sockets per server. Approximately $47,500 per processor licence list price. Supports all advanced options (Partitioning, RAC, Advanced Security, etc.). Required for high-volume OLTP and EE-only features.
Licensing Metrics: Processor vs. Named User Plus
Processor Licensing
Based on hardware resources: CPU cores multiplied by Oracle Core Factor. Most x86 processors have a 0.5 core factor (2 cores = 1 licence). Practical choice when user counts are indeterminate or very large (public-facing systems, hundreds or more users).
Named User Plus (NUP)
Based on counting individual users/devices accessing the database. Cost-effective for limited, identifiable populations. Minimum NUP counts apply: 25 NUP per processor for EE, 10 NUP per server for SE2. Every human or non-human device accessing the database must be licensed.
Cost Structure
| Component | Enterprise Edition | Standard Edition 2 |
|---|---|---|
| Licence metric | Per CPU core (x Core Factor) | Per socket (max 2 sockets) |
| List price per unit | ~$47,500 per processor | ~$17,500 per socket |
| Annual support (22%) | ~$10,450 per processor/year | ~$3,850 per socket/year |
| Min NUP per processor | 25 Named User Plus | 10 Named User Plus |
| NUP licence price | ~$950 per user | ~$350 per user |
| Optional packs/options | Available (licensed separately per same metric) | Not available (EE-only) |
Optional Packs & Database Options
Beyond the base database licence, Oracle offers add-on options and management packs for Enterprise Edition. Each with its own licence cost per the same metric as the database. If you use an option on an EE database with 8 processor licences, you must purchase 8 option licences.
| Option / Pack | List Price/Proc | Purpose | Common Pitfall |
|---|---|---|---|
| Partitioning | ~$11,500 | Large table management & query performance | Enabled "for testing" and left on |
| Diagnostics Pack | ~$7,500 | Performance diagnostics (AWR reports, ASH) | AWR reports run without pack being licensed |
| Tuning Pack | ~$5,000 | SQL tuning advisor, automatic SQL profiling | DBAs use via OEM without realising it needs a licence |
| Advanced Security | ~$15,000 | Transparent Data Encryption, key management | Encryption enabled for compliance without licensing |
| Real Application Clusters | ~$23,000 | Active-active clustering for HA | Every node in cluster must be fully licensed |
| Active Data Guard | ~$11,500 | Read-only standby for DR | Opening standby for reads without licensing |
| Multitenant | ~$17,500 | Pluggable database architecture | Exceeding 3 PDB free limit triggers full licence |
| Database In-Memory | ~$23,000 | In-memory column store for analytics | Enabling IM column store for testing |
Licensing Complexity & Compliance
Oracle's contracts allow the company to audit a customer's software usage, typically with 45-day notice. Oracle is known for aggressive enterprise audits on a regular cycle. Non-compliance can result in backdated licence fees, penalties, and required purchases at list price.
Hardware Overreach
Deploying Oracle on hardware with more cores than anticipated without adjusting licences. Spinning up VMware VMs without accounting for Oracle's policy of licensing the underlying physical hosts.
Feature Creep
DBAs unknowingly using features tied to licences. Running a performance report that relies on Diagnostics Pack, enabling Partitioning syntax in dev databases, or using Oracle Enterprise Manager pack features.
Over-Licensing / Shelfware
Retaining unused licences and paying maintenance on software that isn't utilised. Due to fear of shortfall, past purchasing bundles, or cancelled projects. 22% annual support on idle licences is wasted budget.
Metric Mismatch
Confusing Processor vs. NUP metrics, miscounting users for NUP licensing, or failing to account for non-human devices (batch jobs, interfaces) that access the database and must be licensed.
02 Key Risks & Cost Drivers
Over-Provisioning Enterprise Edition
Reflexively using EE for all databases, even workloads that don't need its features. EE's core-based licensing (2 to 3x cost of SE2) leads to "licence sprawl" where dozens of underutilised EE licences rack up support costs annually.
Unnecessary Costly Options
Optional add-ons (Partitioning, Advanced Security, RAC, Diagnostics Pack) quietly become huge cost multipliers. Each option licensed per processor. Enabling several on one database can triple licence requirements.
Inadvertent Licence Usage
Accidentally using a feature not licensed. Running an AWR report invokes Diagnostics Pack; using SQL Tuning Advisor requires Tuning Pack. Oracle doesn't distinguish intent: if used even once, it's considered requiring a licence.
Hardware Core Count Explosion
Modern servers pack increasing CPU cores, and EE licensing costs scale linearly. A server with twice the cores doubles the required licences. Upgrading hardware without considering licence impact causes costs to skyrocket.
Virtualisation "Licence Shock"
Oracle requires licensing all physical cores in a host or cluster where the software might run. In VMware, if Oracle DB runs on any host in a cluster, every physical server in that cluster must be fully licensed.
Audit Frequency & Penalties
Oracle consistently ranks among the top vendors in audit activity. Financial impact of an adverse audit finding can be severe. Sometimes millions in backdated licence fees, penalties, and required list-price purchases.
Shelfware & Support Waste
Organisations that over-bought or left older deployments on support without active use. At 22%/year, maintaining unused licences is ongoing budget bleed. Common after M&A or cancelled projects.
Lack of Centralised Governance
Without clear governance, siloed decisions lead to non-compliant setups or unnecessary EE deployments. DBAs don't understand licensing implications; architects don't consider licence impact in server design.
Vendor Shield: Oracle Licence Assessment
Our ex-Oracle advisors provide independent licence assessments covering edition alignment, option usage, core factor optimisation, and compliance risk. Typically identifies 30%+ savings opportunities.
03 Strategic Recommendations
Right-Size Edition Usage (SE2 vs. EE)
Match the edition to each workload's true needs. Treat Enterprise Edition as a premium resource to be used only where justified. SE2's socket-based licensing yields huge savings: two 16-core CPUs in a server still count as only "2 processors" under SE2, versus potentially 8 licences in EE (with 0.5 core factor). Reserve Enterprise Edition for systems that truly require it: high-volume OLTP needing maximum performance/scalability, or applications relying on EE-only features.
Govern the Use of Costly Options & Packs
Establish strict guidelines for enabling any optional Oracle Database feature that incurs an extra licence. Insist on a business case and cost-benefit analysis before approving options like Partitioning, Advanced Security, Database In-Memory, or management packs. If the decision is made to use an option, ensure the licensing team is aware so licences are purchased from day one. Many CIOs choose to disable unlicensed packs by default by setting CONTROL_MANAGEMENT_PACK_ACCESS = NONE.
Prevent Inadvertent Usage: Implement Controls
Set CONTROL_MANAGEMENT_PACK_ACCESS = NONE on instances where Diagnostics/Tuning Packs are not licensed. Configure Oracle Enterprise Manager to not display or collect data for unlicensed packs. Remove or disable OEM agents/plugins that could enable pack features. Restrict user access to Partitioning, Advanced Security, or other EE-only features at the database level. Educate DBAs and developers on what features are off-limits without proper licensing.
Leverage Oracle's Core Factor: Optimise Hardware
Work with infrastructure architects to align hardware selection with licence efficiency. Review Oracle's official Core Factor table when planning new database server deployments. Favour processors with a lower core factor (most Intel/AMD x86 chips = 0.5) compared to RISC/Unix chips (often 1.0), which effectively cuts licence requirements in half. If a workload can achieve required throughput on 8 cores, avoid deploying it on a 32-core server. Oracle doesn't let you partially licence a physical server without approved hard partitioning.
Consolidate Databases & Use Multi-Tenancy
Instead of deploying every database on a separate server (each needing its own licences), run multiple databases on the same Oracle server to fully utilise its capacity. Oracle's multi-tenant architecture (12c+) allows a single container database (CDB) to host multiple pluggable databases (PDBs). In Oracle 19c, you can run up to 3 user-created PDBs per CDB without the Multitenant licence option. If you exceed the 3 PDB limit, Oracle requires purchasing the Multitenant option.
Architect for Licence Efficiency (HA/DR & Virtualisation)
Design high availability and disaster recovery architecture with licensing in mind. RAC requires full licensing of each cluster node; Active Data Guard requires additional licensing for read-only standby access. If these aren't strictly required, consider simpler approaches (cold standby, storage replication). For virtualisation: isolate Oracle databases to a smaller dedicated cluster instead of licensing a 10-host VMware cluster. Use Oracle VM or recognised hard partitioning methods where they fit your operational model.
Monitor, Audit, and Adjust Continually
Treat Oracle licence management as an ongoing process, not a one-time exercise. Implement regular internal audits of Oracle usage (at least annually). Use Oracle's LMS scripts or third-party tools to scan databases and identify feature usage, option usage, and configurations. Maintain a clear inventory of licences owned versus deployed. Keep an eye on Oracle's licensing policy updates.
Consider BYOL & Cloud Transition Plans
If your organisation is contemplating moving Oracle databases to the cloud (OCI, AWS, Azure), leverage existing on-premises licences through Oracle's Bring Your Own Licence (BYOL) programmes to avoid double-paying. Oracle's BYOL to PaaS allows applying licences to Oracle's Database Cloud services at reduced cost. On AWS/Azure, Oracle has specific vCPU-to-licence conversion formulas. Do not pay twice for the same Oracle capability.
04 CIO Action Plan: 8 Steps
To implement the above strategies, CIOs should initiate a structured programme for Oracle licence optimisation.
Inventory All Oracle Deployments
Document the edition (SE2 or EE), version, underlying hardware (core count, processor type, physical/virtual), and any options or management packs enabled for each instance. This is the foundation for all optimisation efforts.
Assess Edition Alignment
For each instance, evaluate whether its current edition is appropriate. Identify candidates to downgrade from EE to SE2 (servers with low core counts, applications without EE-only features). Quantify the cost savings of each potential move.
Audit Feature and Option Usage
Using Oracle's audit scripts or licence management tools, scan each EE database for usage of optional features/packs. Cross-check against purchased licences. Address compliance gaps immediately: either procure the licence or disable the feature.
Enforce Controls on Unlicensed Features
Configure CONTROL_MANAGEMENT_PACK_ACCESS = NONE on all instances without licensed packs. Disable OEM agents for unlicensed features. Communicate clearly to DBAs which features are off-limits. Establish a policy requiring licence impact review for any new feature usage.
Optimise Infrastructure for Licensing
Review hardware choices and existing setups. Develop a plan to reallocate Oracle workloads onto fewer, efficiently sized servers. Isolate Oracle VMs to smaller dedicated clusters. Create architecture standards favouring processors with lower core factors.
Review Licence Contracts and Support Renewals
Identify shelfware (owned but undeployed licences). Decide if they can be cancelled (saving support costs) or repurposed. Prepare for support renewal well in advance. Oracle is more flexible when you proactively right-size.
Educate and Govern
Establish an ongoing governance mechanism (quarterly reviews, Oracle Licence Management Office role). Train DBAs, architects, and project managers on Oracle licensing basics. Bake licence impact assessment into every project involving Oracle.
Explore BYOL for Future Cloud Use
Inventory which licences could port to cloud deployments. Understand conversion ratios for AWS/Azure/OCI. Include licence portability in your Oracle strategy now, even if cloud moves are years away. Maintaining flexibility gives you options.
Licence Management
Service
Audit Defence
Service
Contract Negotiation
Service
ULA Optimisation
Service
Frequently Asked Questions
Use SE2 for databases that don't require EE-only features (Partitioning, RAC, Advanced Security, etc.) and can run within SE2's limits of 2 CPU sockets and up to 16 threads. This includes departmental applications, branch office systems, development/test environments, and many production systems with standard requirements. Reserve EE for mission-critical systems requiring maximum scalability, EE-only features, or more than 2 sockets of processing power.
Oracle's Core Factor table assigns a multiplier to each processor family. For most modern Intel and AMD x86 processors, the core factor is 0.5, meaning 2 cores count as 1 processor licence. For IBM POWER or certain RISC/Unix processors, the factor is 1.0, meaning each core counts as a full licence. This directly impacts cost: 8 cores on x86 (factor 0.5) = 4 licences x $47,500 = $190,000. The same 8 cores on POWER (factor 1.0) = 8 licences x $47,500 = $380,000. Standardising on x86 hardware for Oracle workloads can halve your licence costs.
The most common compliance risk is inadvertent use of unlicensed features, particularly the Diagnostics Pack and Tuning Pack. Running an AWR report, using SQL Tuning Advisor, or viewing certain performance screens in Oracle Enterprise Manager all invoke these packs. Oracle doesn't distinguish intent: if a feature was used even once, it's considered requiring a licence. The best defence is setting CONTROL_MANAGEMENT_PACK_ACCESS = NONE on all databases where these packs aren't licensed, and educating DBAs on what's off-limits.
Oracle's stance is that if Oracle Database runs on any VM in a VMware cluster, every physical server in that cluster must be fully licensed, regardless of how many vCPUs the VM uses. This can lead to "licence shock" in virtualised data centres. The mitigation strategy is to isolate Oracle VMs to a smaller, dedicated cluster (e.g., 2 hosts instead of licensing a 10-host cluster). Alternatively, use Oracle VM or other recognised hard-partitioning technologies that Oracle accepts for limiting the licensing scope.
Yes. Oracle 19c allows up to 3 user-created pluggable databases (PDBs) per container database (CDB) without purchasing the Multitenant option licence. This is a powerful consolidation tool: you can effectively run 3 separate application databases on one set of licences. If you need more than 3 PDBs per CDB, the full Multitenant option must be licensed (~$17,500 per processor). Many organisations maximise the free PDB allowance per server and create multiple CDBs to consolidate more databases.
Organisations implementing comprehensive optimisation (edition right-sizing, option governance, hardware optimisation, database consolidation, and virtualisation changes) typically achieve 30% or more reduction in Oracle licensing spend over time. Quick wins include: downgrading non-critical databases from EE to SE2 (60%+ savings per server), disabling and de-licensing unused options (eliminating multiplied costs), and consolidating databases using multi-tenancy (reducing total licensed servers).
📚 Related Reading
Oracle Database Licensing Cost Reduction Guide → Oracle On-Premises Licensing Agreements: CIO Playbook → Oracle Licence Review: Best Practices → Oracle Compliance: Financial Risks → CIO Playbook: Oracle Cloud@Customer Strategy → Oracle Database Licensing on AWS →Optimise Your Oracle Database Licensing
Our ex-Oracle advisors help enterprises right-size editions, govern options, consolidate databases, and prepare for audits. Independent, fixed-fee advisory that typically delivers 30%+ savings.