OCPU-to-licence mapping, BYOL vs Licence Included decision framework, autoscaling guardrails, edition and option entitlement mapping, hybrid multi-cloud governance, OCI native tools, automated compliance scripts, and audit readiness.
Part of the Oracle OCI (Cloud Infrastructure) Licensing guide series. See also: Oracle BYOL on OCI Explained · OCI Pricing and Oracle Licensing.
Oracle Cloud Infrastructure uses the OCPU (Oracle CPU) as its fundamental compute unit. One OCPU equals one physical processor core with hyper-threading, which presents as two vCPUs. The licensing implication is direct: one OCPU requires one Oracle Processor licence. This one-to-one mapping is OCI's principal licensing advantage over third-party clouds, where the same workload typically requires twice as many licences.
OCI offers two licensing models for Oracle software workloads. Under Bring Your Own Licence (BYOL), the customer applies existing on-premises licence entitlements to OCI deployments, paying only for cloud infrastructure. Under Licence Included, Oracle bundles the software licence cost into the OCI service rate. The choice between these models is the single most consequential licensing decision in any OCI migration, and it should be made per workload based on existing entitlement coverage, not as a blanket policy.
On OCI, each OCPU consumed requires exactly one Oracle Processor licence. This is the most licence-efficient cloud platform for Oracle workloads. AWS and Azure require one licence per two vCPUs (equivalent to one OCPU), but OCI's core factor advantage means fewer total licences needed.
BYOL reduces OCI service costs by 30–50% compared to Licence Included pricing for the same compute shape. However, BYOL shifts compliance responsibility entirely to the customer. Oracle will not prevent you from deploying more software than your entitlements cover.
Licence Included pricing bundles the Oracle software licence into the hourly OCI rate. This simplifies compliance (Oracle manages the licence) but costs significantly more per OCPU-hour, making it uneconomical for large, steady-state workloads.
Enterprises running Oracle across OCI, on-premises, and third-party clouds must track licence allocation across all environments. A licence used in OCI under BYOL cannot simultaneously cover an on-premises deployment. Double-counting is a common audit finding.
The OCPU-to-licence mapping on OCI is straightforward in theory. The complexity arises when enterprises run BYOL across multiple environments and lose track of which entitlements are allocated where.
The BYOL-versus-Licence-Included decision should never be made at the organisation level. It must be evaluated per workload. The optimal model depends on three factors: whether you own sufficient existing licences, the workload's runtime pattern (steady-state versus burst), and total cost of ownership over the contract term.
| Factor | BYOL | Licence Included |
|---|---|---|
| When to use | You own sufficient licences and the workload runs continuously | You lack licences or the workload is temporary/burst |
| OCI hourly rate | Lower (infrastructure only) | Higher (infrastructure + licence fee) |
| Compliance responsibility | Customer — you must prove entitlements | Oracle — licence is bundled in the service |
| Audit exposure | Full — Oracle can audit BYOL deployments | Minimal — Oracle manages the licence component |
| Flexibility | Fixed to your entitlement pool — cannot exceed owned licences | Scale freely — pay per OCPU-hour with no licence ceiling |
| Best for | Production databases, middleware — large, steady workloads | Dev/test, short-term projects, peak overflow |
Before selecting BYOL, confirm that you have sufficient unallocated Oracle Processor licences to cover the OCI deployment. Licences already assigned to on-premises servers cannot be simultaneously used in OCI.
For each workload, compare the annual cost of BYOL (OCI infrastructure + annual support) against Licence Included pricing. BYOL is almost always cheaper for 24/7 workloads, but Licence Included may win for workloads running less than 30–40% of the time.
BYOL for Oracle Database Enterprise Edition does not automatically include options like Diagnostics Pack, Tuning Pack, or Advanced Security. Each enabled option requires its own licence entitlement. Failing to account for these is the most common BYOL compliance gap.
Short-lived development and testing environments benefit from Licence Included pricing because they avoid consuming production licence entitlements and can be provisioned and decommissioned without licence tracking overhead.
OCI's elastic infrastructure is designed to scale, which is precisely what creates licensing risk. Every time a compute instance is resized, an autoscaling policy adds OCPUs, or a new database is provisioned, the licence requirement changes. Without continuous tracking, the gap between allocated licences and consumed OCPUs widens silently until an Oracle audit reveals the shortfall.
Create and maintain a master register that maps every OCI compute instance and database service to its OCPU allocation, licensing model (BYOL or Licence Included), and the specific Oracle licence entitlement it consumes. This ledger should be updated automatically through OCI API integration, not manually maintained in spreadsheets.
OCI autoscaling policies can increase OCPU allocation without human approval. For BYOL workloads, configure maximum OCPU limits that align with your licence entitlement ceiling. An autoscaling event that pushes OCPU consumption beyond your licensed allocation creates an immediate compliance gap, even if it lasts only hours.
Use OCI Audit service and event-driven notifications to capture every instance creation, shape change, and scaling event. Route these notifications to the licence management team so that every OCPU-affecting change is reviewed against available entitlements within 24 hours.
Generate automated weekly reports comparing total BYOL OCPU consumption across all compartments and regions against the organisation's total available licence entitlements. Flag any compartment where consumption exceeds 80% of allocated entitlements as a compliance risk requiring immediate review.
Situation: A mid-size insurance company migrated its core Oracle Database Enterprise Edition workloads to OCI using BYOL. The production databases were correctly sized and licensed for their initial OCPU allocations. However, the cloud operations team enabled autoscaling on the primary database cluster to handle quarterly reporting peaks.
What happened: During two consecutive quarter-end reporting cycles, autoscaling increased the database cluster from 8 OCPUs to 12 OCPUs for approximately 72 hours each time. The organisation owned only 8 Processor licences for this deployment.
Result: An internal compliance review identified the gap before Oracle's audit team did. The company implemented OCPU ceiling controls and acquired 4 additional Processor licences to cover peak demand, avoiding what would have been a $190,000 compliance finding.
Takeaway: Autoscaling and BYOL are fundamentally incompatible unless OCPU ceilings are explicitly configured to stay within licensed limits. Every OCPU added by autoscaling requires a corresponding licence.
BYOL compliance on OCI extends far beyond simply matching OCPU counts to Processor licences. Oracle's licensing model includes multiple layers of entitlement that must all align: the software edition, the enabled options and packs, the licence metric, and the territorial and entity scope defined in the ordering documents.
Diagnostics Pack and Tuning Pack are enabled by default in many Oracle Database configurations. If your BYOL entitlements do not include these packs, every BYOL database with them enabled is non-compliant. Oracle's audit scripts specifically detect this. High Risk.
Deploying Enterprise Edition features (RAC, Data Guard with specific configurations, In-Memory) on instances covered by Standard Edition 2 licences. OCI does not prevent you from provisioning EE services under SE2 BYOL. The compliance gap is invisible until audit. Medium Risk.
Named User Plus (NUP) licences have minimum user requirements per Processor (25 NUP per Processor for EE). In OCI, this means each OCPU requires a minimum of 25 NUP, and actual connected users may push the requirement higher. Governance Gap.
Confirm that the Oracle Database edition provisioned in OCI (Standard Edition 2 or Enterprise Edition) matches the edition specified in your licence ordering documents.
Run SELECT * FROM DBA_FEATURE_USAGE_STATISTICS on every BYOL database to identify which options and packs are actively used. Cross-reference against your licence entitlements. Disable any feature you are not licensed for.
Maintain a documented allocation table that assigns specific licence certificates (by ordering document number) to specific OCI instances. This prevents double-allocation and provides audit evidence.
If licensing by Named User Plus, ensure that each OCPU is covered by at least 25 NUP (for Enterprise Edition) or 10 NUP (for Standard Edition 2), and that the actual user count does not exceed these minimums.
Oracle licences often restrict deployment to specific legal entities or geographies. Confirm that your OCI region and the legal entity operating the workload are within the scope of the licence grant.
Oracle Cloud Infrastructure provides several native capabilities that, when properly configured, create an automated governance framework for licence compliance. Most enterprises use these tools for cost management without extending them to licence tracking, a missed opportunity that leaves compliance dependent on manual processes.
| OCI Tool | Licence Governance Application | Configuration Requirement |
|---|---|---|
| OCI Monitoring | Track OCPU utilisation per instance; alert when BYOL instances approach licence ceiling | Create custom alarms on CpuUtilization and OCPUCount metrics |
| OCI Audit Service | Capture every instance creation, shape change, and scaling event for licence audit trail | Enable audit logging in all compartments; route to centralised SIEM |
| OCI Tagging | Label every resource with licensing model (BYOL/LI), licence certificate number, responsible team | Implement mandatory tag namespaces; enforce via IAM policies |
| OCI Quotas | Prevent teams from provisioning OCPU capacity beyond allocated licence entitlements | Set compartment-level OCPU quotas aligned to BYOL licence pools |
| OCI Usage Reports | Generate weekly/monthly OCPU consumption summaries for licence reconciliation | Schedule automated report generation; integrate with SAM tooling |
| OCI Licence Manager | Track BYOL entitlements against deployed resources in a single dashboard | Opt in via Governance & Administration; upload licence entitlement data |
OCI provides the tools to automate licence governance, but they are configured for cost management by default, not compliance. Extending them to track BYOL entitlements requires intentional design.
Manual licence tracking in a dynamic cloud environment is unsustainable. OCI's comprehensive API surface enables enterprises to build automated compliance checks that run continuously, flagging discrepancies before they become audit findings.
Use the OCI Compute API (ListInstances and GetInstance) and Database API (ListDbSystems) to enumerate all running instances and their OCPU allocations across every compartment and region. Schedule this collection daily and compare the results against your licence entitlement register.
Write scripts that query Oracle Database instances via SQL (DBA_FEATURE_USAGE_STATISTICS, V$OPTION) to detect when licensed-only features are enabled without corresponding entitlements. Run these checks weekly. Common drift scenarios include Diagnostics Pack activation through Enterprise Manager and Partitioning used in ETL workloads.
Implement OCI IAM policies and custom functions that prevent provisioning of BYOL resources when the aggregate OCPU consumption in a compartment would exceed the licence allocation. This "pre-provisioning check" catches compliance violations before the instance is created.
Situation: A technology company with 200+ OCI instances across four regions implemented an automated weekly OCPU reconciliation script using OCI APIs. The script compared BYOL OCPU consumption against the company's Oracle entitlement register and flagged discrepancies.
What happened: Within the first month, the script identified 34 OCPU overruns across development and staging environments where teams had provisioned larger-than-authorised shapes. It also detected 12 instances where Diagnostics Pack was enabled on databases covered only by base Enterprise Edition licences.
Result: Compliance gaps were remediated within two weeks. Instances were right-sized, unauthorised features were disabled, and the licence allocation register was updated. Total exposure eliminated: $2.4 million, which would have been Oracle's compliance claim had these gaps been discovered during an audit.
Most enterprises do not run Oracle exclusively on OCI. The typical Oracle estate spans on-premises data centres, OCI, and one or more third-party clouds. Each environment has different licensing rules, and Oracle's audit team evaluates compliance across all environments simultaneously.
Assigning the same Oracle Processor licence to both an on-premises server and an OCI BYOL instance. Oracle's audit methodology identifies this immediately and counts both deployments as requiring separate licences. Critical Risk.
On OCI, 1 OCPU = 1 licence. On AWS, 2 vCPUs = 1 licence (with hyper-threading). On-premises, the Core Factor Table applies. Enterprises must track the correct conversion for each environment separately. Common Gap.
A single, authoritative licence allocation register that tracks every Oracle licence across all environments with clear assignment preventing any single licence from being claimed in multiple locations. Best Practice.
| Environment | Oracle Processor Licence Rule | Core Factor? | Licence Included? |
|---|---|---|---|
| OCI | 1 OCPU = 1 Processor licence | No (1:1 mapping) | Yes — all Oracle services |
| AWS EC2 | 2 vCPUs (HT on) = 1 Processor licence | No | SE2 only (via RDS) |
| Azure | 2 vCPUs (HT on) = 1 Processor licence | No | No |
| On-Premises (Intel) | 1 core × 0.5 core factor = 0.5 Processor licence | Yes | N/A |
The same physical compute capacity requires different licence quantities depending on the environment. OCI is the most efficient; on-premises with core factor is next; AWS/Azure require the most.
Effective OCI licence management requires more than tools and scripts. It requires a governance framework that defines policies, assigns accountability, and ensures continuous compliance rather than periodic fire drills before Oracle audits.
Implement OCI IAM policies that require licence-model tagging before any compute or database instance can be provisioned. Use compartment quotas to enforce OCPU ceilings per licence pool. Mandate approval workflows for any BYOL deployment that would consume more than 10% of remaining available entitlements.
Deploy automated OCPU reconciliation scripts (daily), configuration drift detection (weekly), and entitlement utilisation reports (monthly). Integrate all alerts into a centralised compliance dashboard accessible to IT governance, procurement, and legal teams.
Require that every OCI shape change, autoscaling policy modification, or new workload migration includes a licence impact assessment. Cloud operations should not change OCPU allocations for BYOL workloads without sign-off from the licence management function.
Maintain a standing audit evidence package that includes: licence entitlement certificates, OCPU allocation register, BYOL deployment inventory, configuration compliance reports, and historical OCPU usage data. This package should be refreshable within 48 hours of an Oracle audit notification.
Provisions and manages OCI resources. Applies licence-model tags at provisioning. Escalates any OCPU change that affects BYOL allocations to the licence management function.
Maintains the unified entitlement register. Runs reconciliation reports. Identifies compliance gaps. Manages Oracle ordering document archive.
Manages the Oracle commercial relationship. Negotiates licence purchases when gaps are identified. Coordinates audit response with legal.
Owns the licence governance policy. Reviews compliance dashboards monthly. Approves budget for licence remediation when gaps are identified.
Licence management in OCI is not only a compliance exercise. It is a cost optimisation lever. Enterprises that actively manage their Oracle licence allocation typically achieve 20–35% lower total Oracle costs compared to those that treat licensing as a passive compliance obligation.
Many enterprises over-allocate BYOL licences to OCI "just in case." This leaves surplus licences idle while still incurring 22% annual support costs. Conduct quarterly reviews of actual OCPU utilisation versus allocated licences and reclaim underutilised entitlements.
Oracle's Support Rewards programme grants 25–33% of OCI consumption spend as credits that offset annual support fees. Concentrate Oracle workloads on OCI (where each dollar generates credits) and apply accumulated credits against your largest support renewals.
OCI migrations frequently reveal on-premises Oracle licences that are no longer needed. These surplus licences can be reallocated to other workloads, reducing the need for new purchases, or placed into a dormant support state to reduce annual costs.
| Optimisation Strategy | Typical Annual Savings | Effort Level |
|---|---|---|
| Right-sizing BYOL allocations | 10–20% reduction in support spend on over-allocated licences | Medium — requires quarterly reconciliation |
| Support Rewards maximisation | 25–33% credit against annual support renewal | Low — automatic with OCI consumption |
| Shelfware elimination post-migration | $50K–$500K+ per year depending on estate size | High — requires full entitlement and deployment audit |
Combined impact: 20–35% total Oracle cost reduction. This is a sustained programme, not a one-time exercise.
Oracle's audit scope explicitly includes OCI deployments, particularly BYOL instances. Oracle's LMS and GLAS teams have direct visibility into OCI environments through Oracle's own tooling, which means discrepancies between your claimed BYOL entitlements and actual OCI consumption are more easily detected than in third-party cloud environments.
Every BYOL instance must be mapped to a specific Oracle ordering document with sufficient Processor licence or NUP entitlements.
Retain at least 12 months of OCPU consumption data per instance to demonstrate compliance over time, not just at the point of audit.
For every BYOL database, maintain current output from DBA_FEATURE_USAGE_STATISTICS showing which features are enabled and whether they are licensed.
Ensure every OCI resource is correctly tagged with its licensing model. Mis-tagged resources (e.g., tagged as Licence Included but actually running under BYOL) create confusion during audits.
A pre-built report that matches total BYOL OCPU consumption to total available Processor licence entitlements is the single most powerful audit defence document.