Oracle Database Licensing Calculator. The buyer side numbers.

Oracle Database pricing looks simple and is not. The list prices are public, the arithmetic is documented, and almost every estate we review still has the calculation wrong in at least two places.

The gap is never the headline rate. It is in how processors are counted, whether user minimums were applied, which options are switched on, and what support has compounded to over the years since anyone last looked.

See the Oracle advisory practice for the full method.

How the calculation actually works

Two licence metrics exist and you pick one per deployment. Processor licensing, which covers unlimited users on defined hardware. Or Named User Plus, which counts people and devices, subject to minimums.

Processor licensing is not a count of cores. You take the physical core count, multiply by the core factor for that processor type, and round up. Getting this step wrong in either direction is the most common error we see.

Enterprise Edition

Enterprise Edition is the full product at $47,500 per processor list, and it is the base on which every option is then priced. That second point matters more than the first.

A discount negotiated on Enterprise Edition does not automatically apply to the options. Estates routinely carry a strong database discount alongside options bought close to list, which produces a blended number nobody intended.

Ask for the discount to apply across the whole stack, and check the order form rather than the proposal to confirm it did.

Standard Edition 2

Standard Edition 2 lists at $17,500 per processor and is licensed by occupied socket on servers with a maximum of two sockets. It is not a cheaper Enterprise Edition, it is a different product with real limits.

It caps the CPU threads a single database can use, and it excludes most of the options outright. For workloads that fit inside those limits it is dramatically cheaper.

The mistake runs both ways. Estates on Enterprise Edition that would fit comfortably in Standard Edition 2, and estates on Standard Edition 2 that have quietly outgrown the socket limit and are now non compliant.

The options

This is where Oracle Database estates actually become expensive. Options are licensed per processor, on the same processor count as the database itself, and they stack.

Partitioning, Real Application Clusters, Advanced Security, In Memory, Active Data Guard, and the Diagnostics and Tuning packs are all separate purchases. An estate running four of them can pay more for options than for the database.

The Diagnostics and Tuning packs deserve specific attention. They are reachable through management tooling that database administrators use routinely, and usage is recorded whether or not anybody made a licensing decision.

Audit your enabled options before anyone else does. This is the single highest value hour available on an Oracle estate.

Named User Plus

Named User Plus lists at $950 per user on Enterprise Edition and counts people and devices authorized to use the database, not concurrent sessions.

The minimum is what catches buyers out. Enterprise Edition requires at least 25 Named User Plus per processor, so a two processor server with twelve actual users is still licensed for fifty.

Work out both metrics before choosing. Named User Plus wins on small, stable, human user populations. Processor licensing wins anywhere with application users, batch processing or unpredictable growth.

The core factor table

The core factor converts physical cores into Oracle processors, and it varies by processor family.

• Intel Xeon. Typically 0.5, so sixteen physical cores count as eight processors.
• AMD EPYC. Typically 0.5, on the same basis.
• IBM POWER. Typically 1.0, so every physical core counts fully.
• Oracle SPARC. Typically between 0.25 and 1.0 depending on the model.
• ARM. Typically 0.5.

The hardware decision is therefore a licensing decision. Moving the same workload from Intel to IBM POWER can double the licence requirement without changing a line of code.

Standard Edition 2 does not use the core factor at all. It is licensed by socket, which is why it behaves so differently on dense modern hardware. See the Oracle core factor table.

The competitive position

Oracle prices with the knowledge that migrating a database is genuinely hard. A competitive position only works if it is specific.

Five alternatives come up repeatedly: Microsoft SQL Server, PostgreSQL, Amazon Aurora, Google Cloud SQL and MySQL. Naming them achieves nothing on its own.

What moves an Oracle negotiation is a costed migration plan for one identified workload, with an effort estimate and a date. Not the whole estate, and not a threat. One workload, priced.

Where the common advice on Oracle Database licensing is wrong

The common advice is to concentrate your negotiating effort on the discount against Enterprise Edition list price, because that is the largest single number on the quote. We disagree. In the estates we rebuild, the discount is rarely the problem. The problem is a processor count calculated from the wrong core basis, options enabled by tooling that nobody licensed deliberately, and a support line that has compounded at around 22 percent a year on a licence position bought a decade ago. Fix the count, audit the options, and address support before you argue about the discount. A modest discount on an accurate, right sized position beats an excellent discount on a position that was wrong to begin with, and the second one also carries audit risk the first does not.

What to do next

Before you calculate anything, work through these.

1. List every server running Oracle Database with its physical core count and processor family.
2. Apply the correct core factor to each, and round up per server rather than across the estate.
3. Pull the list of enabled options and packs on every instance, including anything reachable from management tooling.
4. Check whether any Standard Edition 2 deployment has outgrown the two socket limit.
5. Compare processor licensing against Named User Plus, applying the 25 user per processor minimum.
6. Total the annual support line and project it across your remaining hold period before you renew it.

How we engage on Oracle Database licensing

We engage on Oracle Database three ways.

1. Assessment. We rebuild the processor count on the correct core basis, audit which options and packs are actually enabled, test Enterprise Edition against Standard Edition 2 where the limits allow, and compare processor licensing against Named User Plus.
2. Negotiation. We run the commercial conversation across the licence, the options and the support line, including any unlimited agreement and the Oracle Cloud position.
3. Vendor Shield. Always on cover across Oracle and the wider software estate.

See Vendor Shield, the Renewal Program, and the benchmarking practice.

Redress is independent. Buyer side. Industry Recognized. Five hundred plus enterprise clients. $2B+ in client spend under advisory. Eleven vendor practices. One hundred percent buyer side. Read the related About Us page, the management team page, the locations page, and the contact page.