Oracle BYOL to OCI: Conversion Ratios, OCPU Math, and When It Saves

Bring Your Own License, or BYOL, lets you apply Oracle licenses you already own to OCI services at a reduced cloud rate. The alternative is license included, where Oracle bundles the license into the hourly price.

BYOL only saves money when you own the licenses, keep paying support, and the conversion ratio works in your favor. Each of those has a catch.

What is Oracle BYOL and how does it work?

Oracle BYOL lets you apply licenses you already own to equivalent OCI services and pay only the lower BYOL cloud rate. Oracle describes the program on its Bring Your Own License page.

The license included model is the alternative. Oracle bundles the database license into the OCI hourly price, so you pay one rate and own nothing afterward.

Which licenses are eligible?

• Database Enterprise Edition and Standard Edition 2 are common BYOL candidates.
• Database options such as partitioning may need their own BYOL entitlements.
• Active support on the license is required to use BYOL.

How do BYOL conversion ratios work?

Conversion ratios translate your owned licenses into OCI compute units called OCPUs. The ratio decides how much cloud each license covers.

Ratios are set by Oracle and change over time, so confirm the current values on the OCI price list and your ordering document before you model savings.

Why count OCPUs, not licenses?

The workload runs on OCPUs. Counting owned licenses without converting to OCPUs is the most common BYOL sizing error and overstates what you can run.

When does BYOL beat license included?

BYOL beats license included when you own supported licenses and the workload runs steadily. License included wins for short, spiky, or new workloads where you own nothing.

Why does steady workload favor BYOL?

A steady workload uses the converted OCPUs continuously, so the lower BYOL rate plus existing support beats the bundled premium of license included. The eligible editions are set out in the Oracle Licensing Information documentation.

Why does bursty workload favor license included?

1. Estimate the hours the workload actually runs.
2. Compare BYOL rate plus support against license included for those hours.
3. Pick license included when idle support cost outweighs the BYOL discount.

White Paper · Oracle

The Oracle Buyer Side Framework

The moves we use across Oracle Database, Java and ULA estates. Read it free.

Read the white paper

What are the common BYOL traps?

The traps are paying twice and converting wrong. Both quietly erase the saving BYOL promised.

How do you avoid double paying?

Do not keep paying support on licenses that no longer back any workload, per the Oracle support terms. Idle supported licenses used for BYOL math you never deploy are pure cost.

Can BYOL create a compliance gap?

• Track which licenses are committed to OCI BYOL.
• Avoid using the same license on premises and on OCI at once.
• Keep the BYOL allocation documented for any Oracle review.

Where the common advice on Oracle BYOL is wrong

The standard advice is that BYOL is always cheaper than license included because the cloud rate is lower. We disagree. In a large share of the migrations we ran, license included won for short or bursty workloads, because BYOL still requires you to pay ongoing support on the underlying licenses whether the workload runs or not. The buyer side move is to model both options against the real run hours and the support you are already paying, then choose per workload rather than as a blanket policy. A lower hourly rate on idle licenses you keep supporting is not a saving. It is two bills for one workload, and the support line never sleeps.

What to do next

1. List the Oracle licenses you own and their support status.
2. Confirm the current BYOL conversion ratios on the OCI price list.
3. Convert owned licenses to OCPUs before sizing any workload.
4. Model BYOL plus support against license included per workload.
5. Avoid running the same license on premises and on OCI at once.
6. Document the BYOL allocation for any Oracle review.

Frequently asked questions

What is Oracle BYOL?

Oracle Bring Your Own License lets you apply licenses you already own to equivalent OCI services and pay only the lower BYOL cloud rate, rather than the bundled license included price.

How do BYOL conversion ratios work?

Conversion ratios translate owned licenses into OCI compute units called OCPUs. For example, a Database Enterprise Edition processor license commonly converts to two OCPUs under current terms.

Is BYOL always cheaper than license included?

No. BYOL is cheaper for steady workloads on supported licenses, but license included often wins for short or bursty workloads because BYOL still requires ongoing support on the licenses.

Do you still pay support under BYOL?

Yes. BYOL requires active support on the underlying license. If those licenses no longer back any workload, that support cost can erase the BYOL saving.

Can BYOL cause a compliance problem?

Yes, if the same license is used on premises and on OCI at the same time. Track and document which licenses are committed to BYOL to avoid double use.

Which Oracle licenses are eligible for BYOL?

Database Enterprise Edition and Standard Edition 2 are common candidates, and database options usually need their own BYOL entitlements that match the base ratio.

Why count OCPUs instead of licenses?

The workload runs on OCPUs, so you must convert owned licenses into OCPUs before sizing. Counting raw licenses overstates how much OCI you can actually run.

When did BYOL win in your engagements?

BYOL was the right call about 60 percent of the time, mainly where owned licenses were already fully supported and the workload ran steadily rather than in bursts.