The Oracle price list PDF in 2026. Which document to pull, and how to read and cite it.

There is no single Oracle price list. Oracle publishes at least seven PDFs, each with its own columns, metrics and revision date, and only one covers the line you are disputing. Its cover date, not its URL, identifies the version.

When a buyer tells me they checked "the Oracle price list", my first question is which one, and my second is which date. A quote dispute is usually settled by one row in one PDF, and most teams cannot say which PDF or which revision they used.

This page is about the documents themselves: which PDF to pull, how to read a row, how to prove which revision you relied on, and how to put a line in front of an Oracle sales team without claiming more than it proves.

Which Oracle price list PDF do you actually need?

You need the document that carries your metric, and it is rarely the one someone forwarded to you. Oracle splits its pricing into separate documents by product family, and each one is revised on its own schedule.

Start from Oracle's global pricing and licensing page, which links the current documents. Then go straight to the PDF that holds the line you are arguing about, and ignore the rest.

The documents Oracle publishes

• Technology. The Oracle Technology Global Price List is the document most people mean when they say "the price list". It covers Database, its options, the management packs and middleware.
• Applications. The E Business Suite Applications Global Price List covers on premises application modules, priced per Application User and similar metrics.
• Cloud. The PaaS and IaaS public cloud global price list covers OCI. It is also where the service rates for Cloud at Customer and Dedicated Region appear.
• Java. The Java SE Universal Subscription Global Price List is a separate document with a separate metric and its own revision cycle. Our Java employee tier worked example shows how its bands apply to a real headcount.

These seven are the ones most buyers need, and the list is not exhaustive. Oracle also publishes, for example, a separate Oracle Linux Support and Oracle VM Support Global Price List.

If your program is not on the technology list, search the pricing page before you assume it has no published price.

Where to find part numbers for technology programs

The commercial technology price list prints no part numbers, which becomes a problem when a quote arrives as a list of codes. Oracle's Price List Detail with Part Numbers for United States Public Sector fills that gap for technology programs.

It will not give you your commercial price. It will tell you what an unexplained code on a quote refers to. The copy we pulled in September 2026, dated August 4, 2026, prints the Price List, Part Number, Product Description, License Type or Metric, List License Fee and List Software Update License & Support Fee for each line.

• L103399. Oracle Database Standard Edition 2, Processor, $17,500.
• L103405. Oracle Database Standard Edition 2, Named User Plus, $350.
• A90611. Oracle Database Enterprise Edition, Processor, $47,500.

The public sector document is also the one to read if you buy through a government contract vehicle. How those prices relate to commercial terms is covered in our note on GSA schedule pricing against commercial pricing.

How do you read a single line on the Oracle price list?

Read each line as four facts: what the program is, what unit it is counted in, what the license costs per unit, and what the first year of support costs. Almost every pricing dispute with Oracle starts from one of those four.

The technology list, column by column

The technology list prints paired columns, because the same program can be licensed on two metrics at very different prices.

1. Program name. The exact name matters. "Standard Edition 2" and "Enterprise Edition" are different rows, with different prices and different rules.
2. Named User Plus license. The per user list price for that program.
3. Software Update License & Support. The first year support fee against the Named User Plus price.
4. Processor license. The per processor list price for the same program.
5. Software Update License & Support. The first year support fee against the processor price.

A 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. How processors are counted on your hardware is a separate question, answered by the core factor table and, for SE2, by the socket rules in our Standard Edition 2 guide.

The cloud list, column by column

The cloud document is laid out differently, and it makes better evidence, because it prints an orderable code against every line.

• Part number. A short code such as B89636. This is what appears on a quote and on the ordering document.
• Metric. The unit of measure, for example OCPU Per Hour or Gigabyte Storage Capacity Per Month.
• Pay as you go. The rate with no commitment.
• Annual commitment. The rate under a commitment, which is what a Dedicated Region or Cloud at Customer deal draws against.
• Minimum. Any minimum quantity attached to the line. It is easy to miss, and it often decides the cost of a small deployment.

Always quote the part number. One product name can map to several orderable lines at different prices, while a part number maps to exactly one.

Check the support column with a calculator

The support figure is computed from the license price, and you can prove that on any row in ten seconds.

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 reason. There may also be a repricing you have not been told about.

To skip the transcription step, the Database price list lookup holds all 22 Database lines, already offset corrected and checked against the same rule.

What does the support column on the Oracle price list commit you to?

It tells you what the first year of support costs, and nothing about any later year. The footnote says so 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 goes.

Why first year only changes your model

• You cannot budget from the printed figure. Support is subject to annual adjustment, so the number on the PDF is where the cost starts, and it rises from there.
• The percentage applies to net. Support is calculated on the net license fee you actually paid, so your discount flows through to the support line.
• The document says nothing about repricing. What happens to support on the licenses you keep when you drop others is a contract question.

The clause level analysis of matching service levels, repricing on reduction and reinstatement sits in our Oracle technology price list analysis, and the cost trend is covered in Oracle support costs in 2026. This page stays with the document.

A worked example: what the printed support figure hides

Say you buy 4 Standard Edition 2 processor licenses at a 40 percent discount, and support then rises 4 percent a year. Both percentages are illustrative assumptions. The list price is 4 times 17,500, or $70,000, and the PDF would show 4 times 3,850, or $15,400 of support.

The net license fee is $42,000, and year one support is 22 percent of that, or $9,240. By the end of year 5 you have paid more in support than for the licenses.

Over ten years the same assumptions add up to about $110,936, roughly 2.6 times the license fee, and none of it is visible on the price list.

Two other lines of small print worth reading

• "Subject to change without notice." The list is not a quotation and creates no obligation. Treat it as evidence of a published position on a date and nothing more.
• The reproduction notice. Oracle states the document is its property and that any reproduction in part or in whole is strictly prohibited. That affects how you use it in a deck, covered below.

How do you diff two revisions of an Oracle price list PDF?

You compare the cover dates, then the rows you own, line by line. It matters because the list changes underneath you: the revision you used for the business case is often not the one in force when you sign. The diff is how you prove a program was repriced, renamed or removed.

The filename stays the same while the date changes

Oracle uses durable document ids in its file names: 070617 for the technology list, 070574 for the E Business Suite list and 5028356 for the Java SE list. The URL stays the same while the content behind it is replaced, so the cover date is the only reliable version marker.

1. Download the PDF and rename it with the cover date straight away, for example technology price list 2026 04 16.
2. Record the URL, the download date and the file size in the same folder.
3. Store it in the deal file, where the whole team can find it.
4. Repeat at every revision you hear about, and at minimum before each renewal cycle.

The regional copies are not the same document

Oracle serves the same document from country and region paths, and those copies can carry different revision dates at the same moment. This catches people out more than any other point on this page.

When we checked in September 2026, one file name, technology price list 070617, carried four different cover dates:

• Oracle's main path. September 15, 2026.
• The Latin America and India paths. August 3, 2026.
• The French language Africa path. April 16, 2026, two editions behind.
• The English language Africa path. March 1, 2025, more than a year old.

So "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 still disagree.

The Oracle Linux and Oracle VM support list showed the same split: September 1, 2026 on the main path, June 1 on the Asia Pacific path and January 1 on the European path. A newer cover date does not mean every row moved, so compare the rows you own before you conclude anything.

A five step diff you can run in an hour

1. Open the two revisions side by side and compare the cover dates first. If they match, you are looking at the same document twice.
2. Copy the rows for the programs you own, by exact name, into a spreadsheet with one column per revision.
3. Flag three kinds of change: price moved, metric changed, row disappeared. The third matters most.
4. For any disappearance, check whether the program was renamed, folded into a suite, or retired outright. All three happen.
5. Write a one page note recording what changed, citing both cover dates. That note is the record you carry into the negotiation.

A program that drops off 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. Our summary of the 2026 price list changes tracks what moved this year.

How do you turn the Oracle price list into a negotiation baseline?

Build one sheet that fixes the ceiling before any number arrives from Oracle. It becomes the reference every later figure is measured against, separate from any budget.

The baseline sheet, column by column

Lock the sheet before the first quote lands. A baseline built after you have seen the seller's number is a rationalization of that number.

What the PDF cannot tell you

Three things decide the deal, and none of them appear in the document.

• Your discount. Real transaction prices sit well below list, and the list has no view on where.
• Peer benchmarks. A discount looks generous until you know what comparable enterprises paid. Our Oracle license cost benchmarks cover that side.
• The contract clauses. Matching service levels, repricing on reduction, reinstatement and the annual uplift are all contract terms.

For what those numbers mean in a negotiation, and where Oracle gives ground, read the technology price list analysis. For the five year view of controlling Oracle spend, the Oracle CIO guide sets out the governance and renewal plan.

When to pull the documents in a renewal cycle

How do you cite the Oracle price list as evidence in a negotiation?

Cite it precisely and never overstate what it proves. A price list proves a published position on a date. It does not prove entitlement or obligation, and it does not prove your discount was fair.

Cite it the way an auditor would

1. Name the document. "Oracle Technology Global Price List", never just "the Oracle price list".
2. Give the cover date. The revision date is the version identifier, and the only unambiguous one.
3. Give the URL and the date you retrieved it. Retrieval date matters because the file at that URL will change.
4. Quote the row, not the page. Program name, metric, unit price. Short and checkable.
5. Show your arithmetic. If you assert a support figure, put the division next to it.

A precisely cited row usually ends an argument in one message. A vague appeal to "list price" invites a week of email.

The reproduction notice, and what it means for your deck

The notice on the document claims it as Oracle property and bars copying it in part or in whole. Whatever view your legal team takes, there is a simpler habit that also makes your case stronger.

• Link, do not paste. Point to Oracle's own URL so the other side can verify without relying on your copy.
• Quote minimally. A single row with its source line is fair, checkable and hard to argue with.
• Keep the full PDF internally. Archive it in the deal file for your own audit trail rather than circulating it.

Three arguments the price list actually wins

• Metric confusion. When a quote uses a metric the published list does not carry for that program, the burden shifts back to the seller.
• Support arithmetic. When the support line is not 22 percent of net, the document makes the anomaly visible at once.
• Unannounced reprice. When a program's list price moved between revisions, a dated diff shows it and changes the tone of a "standard uplift" conversation.

The same discipline applies in an Oracle audit. If Oracle puts a price on an audit shortfall, ask which document and which revision each unit price came from, and check those rows yourself.

What will Oracle's account team say about the price list, and how should you answer?

Expect some version of the five lines below, usually in the last month before signature. Each has a short reply built on the document itself.

• "That is an old price list." Reply with the document name, cover date, URL and retrieval date, and ask them to cite the revision they are using the same way. If the dates differ, run the diff on the rows in question.
• "The support line is our standard 22 percent." Agree, then ask 22 percent of what. Support is calculated on the net license fee, so ask for the net fee and the support fee to sit side by side on the ordering document, and do the division yourself.
• "That product has been replaced, you need the new SKU." Ask for the old and new part numbers, the metric on each, and what happens to support on the licenses you already hold, all in writing.
• "List prices go up next quarter, so sign now." The list is subject to change without notice. If the risk is real, the answer is a price hold in the contract, which our note on price holds and uplift caps covers.
• "The code on the quote is the standard part." Look the code up in the public sector detail or the cloud list, confirm the program and metric it maps to, and ask about any mismatch before signature.

Contract wording to ask for

The price list itself binds no one, so the protections you want have to sit in the ordering document. Oracle will not agree to all of them, so decide in advance which ones you will hold out for.

• Part numbers on every line. The ordering document should name the part number and metric for each program, so the order maps to exactly one row of the published list.
• Support stated on net. State the first year support fee and the net license fee it is calculated from, so the support check can be done on the paper you sign.
• A price hold on named part numbers. A fixed unit price for additional quantities over a set period protects a growth plan against list changes.
• A cap on support increases. A written limit on the annual adjustment turns the first year figure into a predictable run rate.

What have we seen in Oracle price list disputes in 2024 and 2025?

Across roughly 35 to 45 Oracle pricing and negotiation engagements I ran in 2024 and 2025, the price list was misused in the same three ways. None of them involved a wrong number on the page.

• Citing an unnamed document. Buyers referred to "the Oracle price list" without saying which document they meant, which let the discussion drift to whichever list favored the seller.
• Losing the baseline. Teams had not kept the revision they relied on. A year later the document had changed, and they had no way to show what the baseline had been.
• Quoting names instead of codes. Teams quoted product names rather than part numbers, and the same product name mapped to several orderable lines at different prices.

Each of these is cheap to prevent: a named document, a stored and dated copy, and a part number on every line. Each is expensive to fix once a quote is on the table and the deadline is close.

Why we do not budget from the Oracle price list

The usual advice is to budget from the Oracle price list because it is the official document. We disagree. In almost every engagement I ran, list price overstated the real license cost by a wide margin, while understating the lifetime support burden, because the printed support figure is first year only by Oracle's own footnote.

Use the price list as evidence: to fix a ceiling, to identify 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 price you pay is actually settled.

A price list is not a price. It is a dated statement of what Oracle published, and cited that precisely it becomes the strongest document in the room.

What to do next

1. Name the document. Identify which of the seven or more documents carries your lines, and stop saying "the price list" in meetings.
2. Archive every revision. Download each relevant PDF, rename it with its cover date, and store it in the deal file with the URL and retrieval date.
3. Build the baseline. Record program, part number, metric, quantity, list price, source and calculated support, and verify the support figure on three rows so your team trusts the rule.
4. Diff before each cycle. Compare against the previous revision you hold and write a one page note on what moved.
5. Map every quote code. Use the public sector part number detail or the cloud list to identify any unexplained code on a quote.
6. Cite rows precisely. Link rather than paste, keep the full PDF internal, and read the technology price list analysis for the clause and metric questions this page leaves out.
7. Benchmark before you sign. Bring in independent Oracle advisory to test the discount and terms against what comparable buyers achieved.

Frequently asked questions