Oracle publishes a family of dated price list PDFs, not a single document. Knowing which one carries your line, what the columns mean, and how to prove which revision you relied on is the difference between a claim and evidence.
There is no such thing as the Oracle price list. There are at least seven separate PDF documents, each with its own columns, its own metrics and its own revision date, and only one of them will cover the line you are arguing about.
This page is about the document itself. Which document to pull, how to read a row, how to prove which revision you relied on, and how to put it in front of a sales team without overreaching.
The one that covers your metric, which is almost never the one you were sent. Oracle splits pricing across separate documents by product family, and each is revised on its own schedule.
Start from Oracle's global pricing and licensing page, then go straight to the document that carries the line you are arguing about.
The Oracle price list family, and what each one carries
| Document | Covers | Part numbers | Revision seen July 2026 |
|---|---|---|---|
| Oracle Technology Global Price List | Database, options, packs, middleware | No | April 16, 2026 |
| E Business Suite Applications Global Price List | On premises EBS application modules | No | November 6, 2025 |
| PaaS and IaaS Public Cloud Global Price List | OCI services, Cloud at Customer, Dedicated Region | Yes | May 7, 2026 |
| Fusion Cloud Service Global Price List | Fusion SaaS subscriptions | Yes | Varies by regional path |
| Java SE Universal Subscription Global Price List | The per employee Java metric | Yes | Revised on its own cycle |
| Engineered Systems Price List | Exadata and engineered hardware | Yes | June 30, 2026 |
| US Public Sector price list detail | Technology programs with part numbers | Yes | Published separately |
The commercial technology price list does not print part numbers, which is a problem when a quote arrives as a list of codes. Oracle does publish a United States public sector price list detail that carries part numbers against technology programs.
Use it as a decoding table. It will not give you your commercial price, and it will let you work out what an unexplained code on a quote is actually referring to.
Read it as four facts, not one price: what the program is, what unit it is counted in, what the license costs per unit, and what the first year of support costs. Every argument you will have starts with one of those four.
The technology list prints paired columns, because the same program can be licensed on two metrics at very different prices.
Worked example from the April 2026 revision. Oracle Database Standard Edition 2 prints 350 for Named User Plus with 77.00 support, and 17,500 per processor with 3,850.00 support.
The cloud document is structured differently, and better for evidence, because it prints an orderable code against every line.
Always quote the part number. A product name can map to several orderable lines. A part number maps to one.
The support figure is not quoted, it is computed, and you can prove that in ten seconds on any row.
If a quote shows a support figure that is not 22 percent of the net license fee on that line, ask why in writing before you sign. There may be a legitimate answer. There may also be a repricing you have not been told about.
The first year only. Oracle prints it plainly: "Prices shown on this price list are annual fees that apply to both perpetual and term licenses for first year support only."
That footnote does more work than any number on the page. The document tells you what year one costs and says nothing about years two through ten, which is where most of the money is.
The clause level analysis of matching service levels, repricing on reduction and reinstatement sits on our Oracle technology price list analysis. This page stays on the document.
Because the price list changes underneath you, and the version you relied on when you built the business case will not be the version in force when you sign. The diff is how you prove a program was repriced, renamed or removed.
Oracle uses durable document ids in the file names, such as 070617 for the technology list and 070574 for the E Business Suite list. The URL stays the same while the content is replaced.
This surprises people. Oracle serves the same document from country and region paths, and those copies can carry different revision dates at the same moment in time.
The consequence is that "we checked the current price list" is not a statement of fact until you say which URL you pulled and on what date. Two people can both be right and disagree.
A program that quietly leaves the list is not automatically a problem for licenses you already own. It is always a problem for a growth assumption, because you can no longer buy more of it at a published price.
By building one sheet that fixes the ceiling before any number arrives from Oracle. The baseline is not a budget. It is the reference every later figure gets measured against.
Lock the sheet before the first quote lands. A baseline built after you have seen the seller's number is not a baseline. It is a rationalization.
Three things, all of which decide the deal, and none of which appear on the document.
For the analysis of what those numbers mean and where the leverage sits, read the Oracle technology price list analysis. This page is only about the evidence.
By citing it precisely and never overstating what it proves. A price list proves a published position on a date. It does not prove entitlement, it does not prove obligation, and it does not prove your discount was fair.
A precisely cited row ends an argument in one message. A vague appeal to "list price" invites a week of email.
Oracle states the document is its property and prohibits reproduction in part or in whole. Whatever view your legal team takes, there is a simpler and stronger habit available.
The standard advice is to budget from the Oracle price list because it is the official document. We disagree. In nearly every engagement Fredrik Filipsson ran, list price overstated real cost by a wide margin while understating the lifetime support burden the document barely mentions, since the printed support figure is first year only by Oracle's own footnote. The price list is evidence, not a budget. Use it to fix a ceiling, to decode a part number and to prove what was published on a date. Then argue the actual number from benchmarks and contract terms, which is where the money moves.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
A price list is not a price. It is a dated statement of what Oracle published. Cite it that precisely and it becomes the strongest document in the room.
On Oracle's global pricing and licensing page, which links the current documents. Go straight to the specific document that carries your metric, because Oracle publishes separate lists for technology, applications, cloud, Fusion, Java and engineered systems.
No. There are at least seven separate documents, each with its own columns, metrics and revision date. Citing "the Oracle price list" without naming which one is the most common mistake we see, and it lets a discussion drift to whichever list suits the seller.
Because it prints program names against Named User Plus and Processor prices rather than orderable codes. Part numbers appear on the cloud, Fusion, Java and engineered systems lists, and Oracle also publishes a United States public sector price list detail carrying part numbers for technology programs.
No. Oracle's own footnote states the prices are annual fees for first year support only. Support is also calculated on the net license fee you actually paid rather than list, and it is subject to annual adjustment thereafter.
Divide it by the net license fee on the same line. Every row we checked across the technology and applications lists computes to exactly 22 percent. If a quote shows something different, ask for the reason in writing before signature.
By the date printed on the cover. The file name carries a stable document id that does not change between revisions, so the URL alone tells you nothing. Rename every download with its cover date and record the retrieval date.
No. They sit on the PaaS and IaaS public cloud global price list, which prints a part number, a metric, a pay as you go rate, an annual commitment rate and any minimum. Cloud at Customer and Dedicated Region services appear there.
Quote from it rather than reproducing it. Oracle states the document is its property and prohibits reproduction in part or in whole. Link to Oracle's own URL, quote the single row you are relying on with its source and date, and keep the full PDF in your internal deal file.
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 Oracle price list is a ceiling dressed as a price. The buyer who benchmarks against it, and models the 22 percent support multiplier, reads the document the way Oracle hopes you will not.
