The Oracle Database price list for 2026. What changed, and what it costs you.

Oracle's core Database list prices did not change in 2026. Quotes still rose, because the discount Oracle gives against the list keeps shrinking, options were repackaged, and cloud incentives now shape the deal.

Oracle's 2026 technology price list changed far less than the attention it received. The cost changes sit in three places the headline does not show: the discount Oracle will give against the list, the way options are packaged, and the incentives that pull renewals toward an annual cloud metric.

The 2026 list lands on discounts that have been eroding for seven years. Our Vanishing Discount benchmark report tracks the average Oracle discount falling from 57 to 44 percent, and what buyers can still do about it.

What changed in the Oracle Database price list for 2026?

On the core Database lines, almost nothing. Enterprise Edition lists at $47,500 per Processor and $950 per Named User Plus on the edition effective April 16, 2026, and the main options held close to their prior levels. The real changes were in packaging and in the incentives steering buyers toward cloud and subscription terms.

Oracle reissued the Technology Global Price List on August 3 and again on September 15, 2026. We checked the September 15 copy against the March 1, 2020 edition. Enterprise Edition and the six options and packs below carry exactly the same prices in both.

Oracle publishes the current lists as dated PDFs on its corporate pricing page. Model from the dated file and write its effective date into the deal folder. Items are added, retired and repackaged between editions, and regional copies of the same file on oracle.com can carry different cover dates.

For the line by line figures, keep the Oracle Technology Price List guide open beside this page, and use the Oracle Knowledge Hub for the wider topic list.

Where did Oracle prices change, then?

The changes that reach a quote sit around the edges of the list, and they are smaller and harder to spot than a headline increase.

• Stable core. Enterprise Edition and the main options held at prior list levels, including through the two reissues after April.
• Selective rises. A handful of options saw single digit increases instead of a broad uplift.
• Repackaging. Some management packs were regrouped into clearer bundles, which breaks a like for like comparison unless you work from part numbers.

A list frozen for six years is a price cut in real terms. Net prices still went up over the same years, which tells you where Oracle recovered the difference.

How is Oracle steering buyers toward cloud and subscription?

Oracle does it with incentives priced around the list. It uses OCI credits, Support Rewards and bring your own license conversions to make an annual cloud metric look cheaper than perpetual licenses plus support.

• Support Rewards. Each dollar of OCI consumption earns 25 cents of credit against your technology support bill, or 33 cents if you hold an unlimited license agreement. Rewards apply only to technology support renewals, so Java subscriptions, some MySQL subscriptions, Oracle Linux and applications support do not qualify. Our Support Rewards guide works through the numbers.
• Bring your own license. The ratios that carry perpetual entitlements onto OCI sit in Oracle's service descriptions, outside your ordering document, so check the version in force on the day you convert and keep a copy.
• Annual metric. Subscription terms replace a perpetual asset with a renewable one. The saving in year one is real, and by year three your negotiating position has gone with the asset.

None of these appears on the list as a price change, yet each one alters what you pay over the term.

Does the 2026 Database list apply to Oracle applications?

No. Applications sit on their own price lists with their own refresh cycle. If Fusion is in scope, read the Oracle Cloud ERP pricing guide and our analysis of base subscriptions against add on modules alongside this page.

If the list did not change, why is my Oracle quote higher?

Because the discount changed. 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.

Take one purchase of 16 Enterprise Edition Processors: 16 x $47,500 = $760,000 at list. Hold that list completely flat and vary only the discount.

Five year cost is net license plus five years of support at a flat 22 percent, with no annual increase. The gap between the first and last rows is $207,480 on one purchase, and the list price is identical in every row.

A 13 point fall in the achieved discount raised the net license by 30 percent. Each point on this order is worth $7,600 of license and $1,672 a year of support, or $15,960 over five years, and 13 of them make up the gap. Put that figure on the first slide of any internal briefing.

Oracle does not need a price rise when a smaller discount does the same work, and a smaller discount never appears in a price list announcement.

How should you report Oracle price changes internally?

Report net price per unit, per metric, per year. In the example above that is $20,425 per Processor at 57 percent off and $26,600 per Processor at 44 percent off. A report that tracks list movement tracks the number Oracle is least interested in changing.

Restate your last three Oracle purchases this way before the next quote arrives. Discount erosion then shows up as its own line, separate from any list change, and you can set it against our Oracle license cost benchmarks.

How do you compare two Oracle price lists line by line?

Key the comparison on the part number. Every line on the Oracle Technology Global Price List carries a part number alongside the product description, the metric and the two price columns. Product names get reworded, split and merged between editions, so a comparison by name produces false increases and hides real ones.

Build it once as a spreadsheet keyed on part number, keep both source PDFs with their effective dates, and rerun it at every new edition. The same file doubles as audit preparation, because it shows which part numbers you hold and on which metric. Our guide to the Oracle price list PDFs explains which document holds which products.

How do you check what you own and what you use?

The diff tells you what Oracle changed. These records tell you whether the change touches you.

• Ordering documents. Each order states the product, metric, quantity and net fee. They define your license sets and which licenses share a license order.
• Support renewal quote. It lists each Customer Support Identifier and the support fee per line. That is the support base every future repricing starts from.
• DBA_FEATURE_USAGE_STATISTICS. This view records which options and packs each database has used. Oracle's options_packs_usage_statistics.sql script on My Oracle Support summarizes it by option, and our note on running the feature usage report first explains why.
• CONTROL_MANAGEMENT_PACK_ACCESS. This initialization parameter shows whether Diagnostics and Tuning Pack features are enabled on each Enterprise Edition database.

What does Oracle repackaging do to licenses you already own?

It shifts the boundary between what you already own and what you have to buy. That boundary can shift in either direction, and the two directions do not cost the same.

When a feature joins the base product

Nothing is refunded. If a capability you licensed separately becomes part of the base edition in a later release, the option licenses stay on your support renewal until you actively terminate them. The precedent is December 5, 2019, when Oracle included Advanced Analytics and Spatial and Graph with Database, and its FAQ on the change said nothing about refunds.

Terminating those option licenses 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, with a number attached, and do not treat it as paperwork.

When a base feature becomes a separately priced option

This is the expensive direction. A database that has used a base feature for years can fall out of compliance on the day it upgrades to a release where that feature is licensed separately.

• Entitlements follow the release you are licensed for. Check the Licensing Information User Manual for the version you run, which may differ from the current one.
• Feature usage is logged whether or not anyone intended it. An upgrade can create audit evidence before procurement has seen a price list.
• The gap surfaces at audit. Nothing flags it at upgrade time, so put the licensing question on the agenda of the change board that approves the upgrade.

How to test whether a repackaging is real

Ask three questions about every line that looks new, and send them in the same email.

1. Which prior part numbers does this line replace, and are they retired or still orderable?
2. Does your existing entitlement to the replaced part numbers grant use of this line, or is a migration order required?
3. If a migration order is required, at what price, and does the existing support base transfer or restart?

The third question is the one that costs money. A migration that restarts the support base at a new net fee can cost more than the original purchase did.

What stayed the same on Java and Oracle support in 2026?

Java kept its metric and support kept its rate, and those two items set most of the Oracle bill.

Java remains on the per employee Java SE Universal Subscription, introduced on January 23, 2023. It is priced in bands by total employee count, from $15 per employee per month down to $5.25, and it counts your whole workforce, Java users or not. The Oracle Java licensing guide works through the bands and the audit exposure.

Why does the support base matter most?

Support is the only line that repeats every year. It stays at 22 percent of net license fees, and across a multiyear term it becomes the majority of total Oracle spend. In the engagements we have costed, it made up most of the total over a five year hold.

Oracle's support policies allow annual adjustments and set no ceiling on them, so a cap exists only if your ordering document states one. The base you carry into a renewal therefore outweighs any list change published in the meantime. Our Oracle support costs analysis covers how that base grows.

How can a list increase cost you when you buy nothing?

Through the repricing clause in Oracle's Software Technical Support Policies, which is written against list. When you terminate or reduce support on part of an order, "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."

The words "in effect at the time of termination" mean the baseline is whatever the list says on that future date, regardless of the list you originally bought against. The same policy caps the result at your previous support fees plus any annual adjustment, and floors it at what you already paid for the licenses you keep.

• The effect of a list increase. It raises the result of every future reduction, up to that ceiling, including on licenses bought years earlier. For a customer who buys nothing at all, that is a real cost, and it belongs in the renewal model.
• Where to find the arithmetic. The technology price list guide works a full repricing example, and our guide to dropping support covers the reinstatement terms.

What did we see in Oracle pricing reviews in 2024 and 2025?

Across the 40 to 50 Oracle pricing reviews I led with clients between 2024 and 2025, the yearly list change mattered far less than the pull toward cloud. Three patterns came up again and again.

• The list barely shifted. Year on year list changes on core Database stayed within 0 to 8 percent, while the discount offered against that list fell every single year.
• Cloud incentives swung about half the renewals. Roughly one renewal in two moved to an annual metric, usually because Oracle priced the alternative attractively, with the list untouched.
• Support dominated the total. It held at 55 to 70 percent of total Oracle spend over a term, so the base carried into the renewal decided more than any published change.

Why we do not time Oracle purchases around the price list refresh

The common advice is to wait for the new list and time purchases around price changes. We disagree, because the data does not support it. In roughly half of the renewals we benchmarked, the list barely changed, while the cloud incentives and the support base drove the entire outcome.

Ignore the refresh as a timing signal. Negotiate the support base, the option footprint and any cloud conversion on your own schedule, and time the deal against your own position: a live alternative, a decommissioning plan you can execute, and a renewal date you control.

What will the Oracle account team say about the 2026 list?

Expect the conversation to start from the stable list and move quickly to the discount, the bundle or the cloud offer. These are the lines we hear most often, with the reply that keeps the numbers on your terms.

• "List prices did not change, so your pricing is in line with last time." Ask for the quote restated as net price per Processor and compare it with your last order. In the 16 Processor example, the same list gives $20,425 or $26,600 depending on the discount.
• "Discount approvals are tighter this year." Ask which part numbers the discount covers, and request the same discount as a price hold on additional quantities. Bring your own benchmark to that meeting.
• "The new bundle replaces your packs, so you just need a migration order." Send the three repackaging questions in writing, and sign nothing until Oracle states whether your support base transfers.
• "Moving to OCI with Support Rewards will take care of your support bill." Ask for the model across the full term. Rewards accrue only on OCI consumption and offset only technology support, and committed cloud spend is spend you must consume.
• "If you drop those licenses, the rest will be repriced." Ask for the repriced quote in writing, showing list support, the standard discount used, and the ceiling and floor.

What price protection can you get in writing from Oracle?

More than most buyers ask for, provided you ask before signature. Oracle will rarely volunteer any of the four clauses below, and all four are ordinary commercial requests.

1. A price hold on named part numbers. A stated unit price, valid for a stated period, for additional quantities of the exact parts on this order. Without part numbers it is not a price hold.
2. A support increase cap for the full term. A maximum annual percentage increase that applies beyond the first renewal, with wording that survives any repricing under the reduction clause.
3. A defined reduction right. The percentage of the order you may terminate at a defined renewal date, and the exact support fee that applies afterward, stated as a number instead of a method.
4. Migration protection. If Oracle repackages or retires the part numbers you bought, a right to the successor product at no additional license fee, with the support base carried over.

Clause four is the one that pays for the legal review, because it turns every future repackaging into an administrative step. Our guide to price holds and uplift caps has sample wording for the first two.

How does the 2026 list affect small and large Oracle customers?

The list is the same for everyone, but the exposure differs with the size and shape of what you own. Two situations show the range.

A customer with a few Processors on one or two orders

Each discount point is worth little in dollars, so the repricing clause matters more than the discount. With few lines on each order, terminating part of an order often saves close to nothing once the remaining licenses are repriced. Support Rewards help only if you already run meaningful workloads on OCI.

A large customer with many orders or an unlimited agreement

Repricing works per license order, so the order each license sits on decides what a reduction saves, and the diff should record it. Unlimited license agreement holders earn Support Rewards at 33 cents per dollar. Large customers also carry the most options and packs, which makes the part number diff and the migration protection clause worth the most here.

What to do next

1. Get both lists. Pull the dated 2026 price list PDF and the prior version, record both effective dates, and build the four column diff keyed on part number, flagging every metric change first.
2. Map repackaged options. Trace each one back to your existing entitlements and ask Oracle in writing whether a migration order is required.
3. Restate your purchases. Express your last three purchases as net price per unit, per metric, per year, so discount erosion shows separately from list changes.
4. Recalculate support. Work out support as a share of total Oracle spend over five years, using the 22 percent rate and your own history of annual increases.
5. Model any cloud offer in full. Run every OCI conversion or Support Rewards offer across the whole term, treating committed cloud spend as spend you must consume.
6. Benchmark the discount. Compare your achieved discount with comparable enterprises before you accept the number in front of you.
7. Set your own timetable. Separate renewal timing from the list refresh calendar and plan it around your alternatives, your decommissioning plan and your renewal date. Our Oracle CIO playbook sets out the five year plan.
8. Ask for protection early. Send the four price protection clauses in one email before the commercial conversation narrows to a discount percentage.

Frequently asked questions