What moved on the Oracle 2026 price list, and what it costs you. Core Database held near flat while the achieved discount fell, options were repackaged, and the cloud incentives did the real steering.
Oracle refreshed its technology and cloud price lists for 2026, and the headline numbers matter less than the structural shifts. Core Database list prices barely moved. What moved is the discount Oracle is willing to give against them, the packaging of options, and the incentives pulling buyers onto an annual cloud metric.
The 2026 list increases land on discounts that have eroded for seven years. The Vanishing Discount benchmark report shows the Oracle average discount falling from 57 to 44 percent, and what buyers can still do about it.
This analysis is for buyers modeling Oracle cost against the 2026 list. Read it with the Oracle Technology Price List guide, which carries the current line by line figures, and the Oracle Knowledge Hub.
Less than the attention it gets. Core Database and option list prices moved only modestly, and the meaningful change is the packaging and the steering toward cloud and subscription terms.
Oracle publishes the current lists on its corporate pricing page. Always model from the dated PDF, because items are added, retired and repackaged between refreshes.
Enterprise Edition and the main options held close to prior list levels. A few options saw selective increases, and the management packs were tidied into clearer bundles.
On the part number, never the product name. Every line on the Oracle Technology Global Price List carries a part number alongside the product description, the metric and the two price columns.
The part number is the stable key. Product names get reworded, split and merged between refreshes, so a name based comparison generates false increases and hides real ones.
A four column diff that takes an afternoon and settles most arguments
| Column | Where it comes from | What a change in it means |
|---|---|---|
| Part number | Both price list versions | Missing in the new list means retired or renamed. Ask which, in writing. |
| License metric | Both versions, same row | A metric change is the most expensive kind of change and the least visible. |
| License list price | Both versions, same row | The headline. Usually the least important of the four. |
| Support list price | Both versions, same row | Sets the baseline the repricing clause uses against you later. |
Build it once as a spreadsheet keyed on part number, keep both source PDFs with their effective dates, and rerun it at every refresh. It is the cheapest audit preparation you will ever do.
Through the incentives, not the list. Oracle prices OCI credits, Support Rewards and bring your own license conversions to make the annual cloud metric look cheaper than perpetual plus support.
None of these appear as a price change. All of them change what you pay.
Because the discount moved. Oracle does not need to raise a list price to raise your price, and in the 2024 to 2026 window it mostly has not needed to.
Run the arithmetic on a single 16 Processor Enterprise Edition purchase, 16 x 47,500 = 760,000 dollars at list, with the list held completely flat.
Same list price, different year, on a 760,000 dollar list purchase
| Discount achieved | Net license | Year one support at 22 percent | Five year cost of ownership |
|---|---|---|---|
| 57 percent | 326,800 | 71,896 | 686,280 |
| 50 percent | 380,000 | 83,600 | 798,000 |
| 44 percent | 425,600 | 93,632 | 893,760 |
Five year cost is net license plus five years of support at a flat 22 percent, no uplift. The gap between the first row and the last is 207,480 dollars on one purchase, with the list price identical in every row.
That is the number to put on the first slide. A 13 point fall in the achieved discount raised the net license by 30 percent and the five year cost by 207,480 dollars, while every published price stayed exactly where it was.
It also means the only honest way to report Oracle price movement internally is per unit net, per metric, per year. A report that tracks list movement tracks the number Oracle is least interested in changing.
Oracle does not need a price rise. It needs a smaller discount, and nobody writes a briefing note about that.
It moves the boundary between what you already own and what you have to buy, in both directions, and the two directions are not symmetric.
Nothing is refunded. If a capability you licensed separately becomes part of the base edition in a later release, your existing option licenses stay on the support base until you actively terminate them.
That termination then runs into the repricing clause, so the practical saving is usually far below the option's support line. Raise it at renewal as a negotiation item rather than as a paperwork exercise.
This is the expensive direction. An estate that has been using a base feature for years can become non compliant on the day it upgrades to a release where that feature is separately licensed.
Ask three questions of every line that looks new, and put them in the same email.
Question three is the one that costs money. A migration that restarts the support base at a new net fee can be more expensive than the original purchase.
The two things that set most of the bill. Java licensing did not change metric, and support did not change rate.
Java remains on the per employee Java SE Universal Subscription introduced in 2023, priced in bands by total employee count rather than by Java users. The Oracle Java licensing guide works the bands and the audit posture.
Oracle 2026 list, what moved and what held
| Area | 2026 direction | Buyer impact |
|---|---|---|
| Database Enterprise Edition | Stable at 47,500 per Processor | Anchor unchanged, discount is the variable |
| Options and packs | Repackaged, some single digit rises | Compare on part number or not at all |
| Java SE | Unchanged metric | Per employee still counts the whole workforce |
| Support rate | 22 percent of net, held | Base still compounds, uplift still uncapped |
| Support list price | Moves with the license list | Raises the repricing baseline used against you |
| Cloud incentives | Stronger | Steering to OCI without a list change |
Because it is the only line that repeats. Support is unchanged at 22 percent of net license fees per year, and across a multi year term it remains the majority of total Oracle spend.
In the engagements we have costed, support ran at 55 to 70 percent of the total over a five year hold. The base you carry into a renewal therefore matters more than any list change published in the meantime.
Here is the part almost nobody models. Oracle's support repricing clause is written against list, not against your contract.
Support for the remaining licenses on that license order will be priced at Oracle's list price for support in effect at the time of termination or reduction minus the applicable standard discount.
Read the phrase "in effect at the time of termination". The baseline used when you shrink an estate is whatever the list says on that future date, not the list you bought against.
So a published list increase raises the ceiling on every reduction you might make in future years, even on licenses you bought long before it. That is a real cost of a list rise for a customer who buys nothing at all, and it belongs in the renewal model. The full arithmetic sits in the technology price list guide.
The standard advice is to wait for the new list and time purchases around price changes. We disagree, and the data does not support it: in roughly half of the renewals we benchmarked the list barely moved, while the cloud incentives and the support base drove the entire outcome.
The buyer side move is to ignore the list refresh as a timing signal. Negotiate the support base, the option footprint and any cloud conversion on your own schedule.
Time the deal against your own leverage instead. That means a live alternative, a decommissioning plan you can actually execute, and a renewal date you control. The calendar does not set your price.
Source: Redress Compliance advisory engagement file, 2024 to 2025. The 30 percent is arithmetic from the worked example above, on a 57 to 44 percent discount move.
The annual price list is theater. The support base and the cloud incentive sheet are the script. Negotiate those, and the list change becomes a footnote.
More than most buyers ask for, and only if you ask before signature. Oracle will rarely volunteer any of the four clauses below, and all four are ordinary commercial requests.
Clause four is the one that pays for the legal review. It converts every future repackaging from an exposure into an administrative step.
Applications sit on their own price lists with their own refresh cadence. If Fusion is in scope, read the Oracle Cloud ERP pricing guide and the analysis of base subscriptions against add on modules alongside this page.
Core Database and most options held close to prior list levels, with selective single digit increases on a few items. The more important change for 2026 is structural, with stronger cloud and subscription incentives steering buyers toward annual metrics.
Almost always because the discount fell rather than the list rose. On a 760,000 dollar list purchase, a move from 57 percent off to 44 percent off raises the net license from 326,800 to 425,600 dollars, a 30 percent increase with no list change at all.
Oracle publishes the current technology and cloud price lists on its corporate pricing page as dated PDFs. Model from the dated version and record the effective date, because Oracle adds, retires and repackages items between refreshes without changing the headline list dramatically.
Key the comparison on part number, never on product name. Build four columns for each part: part number, license metric, license list price and support list price. A metric change matters more than a price change and is far easier to miss.
No. Java licensing remains on the per employee Java SE Universal Subscription introduced in 2023. The metric counts your whole workforce rather than Java users, and that did not change in the 2026 refresh.
Yes. Annual support remains at 22 percent of net license fees, with the same repricing rules tied to the support base. Over a multi year contract, support typically becomes the majority of total Oracle spend.
Yes, indirectly, and this is widely missed. The support repricing clause prices remaining licenses at Oracle's list price for support in effect at the time of termination, so a higher published list raises the baseline used against you whenever you reduce an estate.
Oracle prices OCI credits, Support Rewards and bring your own license conversions to make the annual cloud metric look cheaper than perpetual licenses plus support. Model any such offer across the full term before treating it as a saving.
Generally no. The list moves little year on year, so timing around it rarely helps. Your leverage, the support base and competitive pressure set the real price far more than the calendar of list updates.
When Oracle rebundles options or management packs, a line that looks new may simply be a regrouping of features you already license. Ask which prior part numbers the line replaces, and whether a migration order is required before you accept that a price has changed.
The support base. Because support compounds at 22 percent of net fees every year, reducing the licensed base you carry moves total cost far more than any list price change. Terminating unused licenses is the lever, subject to the repricing clause.
The governance, renewal and negotiation moves that hold Oracle cost across a five year horizon.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The annual price list is theater. The support base and the cloud incentive sheet are the script. Negotiate those, and the list change becomes a footnote in your renewal.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One short note on Oracle licensing moves, price list mechanics, audit posture, and the buyer side levers we are running in client engagements. No noise.
