Oracle Database licensing. Every price, metric and rule in one place.

This page is the lookup layer for Oracle Database licensing. Every edition, every separately priced option, every management pack, both metrics, the minimums, and the counting rule for each platform, with the list numbers next to them.

It is deliberately not the argument. For the case behind a position, what it costs to hold, and how the audit and the renewal actually run, read the Oracle Database licensing pillar. Come back here when you need the number.

Two thirds of the spend on a typical Oracle Database estate sits in options and packs, not in the base edition. So the catalog below is ordered by what it costs you rather than by what Oracle calls it.

Which documents decide what you owe?

Eight documents decide every Oracle Database licensing question, and only three of them are contract. That distinction settles more arguments than any technical fact on this page.

An auditor will quote all eight at you in the same tone of voice. Your job is to know which ones you actually signed up to.

The two documents that are policy and not contract

The partitioning policy and the cloud policy are the two that decide the largest numbers, and neither is normally part of what you signed. Oracle can revise both unilaterally, and has.

That does not make them irrelevant. It changes the shape of the conversation from compliance to commercial, which is a conversation you can win. The full argument sits on the Oracle partitioning policy page.

Where to look a feature up before you argue about it

Start in the Oracle Database Licensing Information User Manual, in the permitted features table for your release. It lists every feature against every edition, and it names the option or pack each feature requires.

Two rules of thumb from using it in anger.

• The software letting you run something is not permission. Almost every priced option installs by default and runs without a key. The manual, not the binary, defines entitlement.
• Read the release you run, not the current one. Feature to edition mappings move between releases, and the auditor will read the manual for your version.

Price every line against the Oracle Technology Global Price List yourself. Our summary of the current document sits on the Oracle technology price list page.

Which Oracle Database edition are you entitled to run?

Four editions are in play in 2026, and most estates only ever discuss two. Enterprise Edition carries the option catalog. Standard Edition 2 carries a fixed feature set with no options at all.

Enterprise Edition costs 2.7 times the SE2 unit price on either metric. The ratio is identical on both because Oracle prices both editions on the same one to fifty Processor to Named User Plus relationship.

The edition matrix

Capability	Standard Edition 2	Enterprise Edition	Free (formerly Express)
Maximum sockets	2 per server	Unlimited	Resource capped, not socket capped
Hard CPU thread cap	16 threads per single server	None	2 CPUs, 2 GB RAM, 12 GB user data
Real Application Clusters	Not available from 19c onward	Available as a priced option	Not available
Partitioning	Not available	Priced option	Not available
Active Data Guard	Manual standby only	Priced option	Not available
Advanced Compression	Not available	Priced option	Not available
Diagnostics and Tuning Pack	Not available	Priced packs	Not available
List price per Processor	$17,500	$47,500	Free
List price per Named User Plus	$350	$950	Free
Minimum	10 NUP per server	25 NUP per Processor	None

The two editions nobody puts in the summary

• Personal Edition. Single user development and prototyping, licensed per Named User Plus with a one user minimum per machine. It carries the full EE feature set including the options, which is why it turns up as an audit surprise on a developer laptop.
• Free. Oracle renamed Express Edition to Oracle Database Free with the 23ai release. Same resource caps, no support contract, no right to run it as a production dependency you then extend. The detail sits on our 23ai licensing guide.

Standard Edition 2 counts an occupied socket as one Processor license, not cores multiplied by a core factor. That is the single largest structural difference in how the two editions are counted, and the crossover arithmetic sits on the Enterprise versus Standard Edition page.

Discount bands by edition

• Enterprise Edition. 35 percent to 70 percent off list, set by volume, term and whether you hold a credible alternative platform. Volume orders typically clear 35 percent.
• Standard Edition 2. 25 percent to 50 percent off list, with narrower bands at scale.
• Free. No charge and no support contract, so no discount conversation exists.
• Cloud BYOL. The same edition price applied at the BYOL conversion rate for the target platform.

What does each Oracle Database option actually cost?

Every priced option carries the same metric and the same quantity as the base database on the server where it runs. Price each one off its own line, because the spread across the catalog is more than a factor of two.

A flat figure of 23,000 USD per Processor gets quoted across the whole catalog often enough to be worth naming. It is the RAC, In Memory and OLAP number, not the catalog number. Applying it to a twelve line stack overstates your position by a wide margin, in Oracle's favor.

The priced option catalog with both metrics

Verify every figure against the current price list before you build a case on it. Oracle revises the document without announcement, and the version that matters is the one in force on your order date.

Two options Oracle stopped charging for, and estates still budget

Oracle moved two former priced options into the base product in 2019, and the change never reached most internal license models. We still find both carried as live cost lines.

• Spatial and Graph. Formerly around 17,500 USD per Processor. Included with all editions since the 19c cycle. Locator was always free and is now moot.
• Advanced Analytics. Formerly around 23,000 USD per Processor. Renamed Oracle Machine Learning and included with the database.

Confirm both against the licensing manual for your release before you strip the line. Then check the reverse case, because the same 2019 cycle also created partial allowances that are easy to overrun.

• Database In Memory Base Level. A column store up to 16 GB per instance without the option on Enterprise Edition, with a reduced feature set. Size past the allowance and the full 23,000 USD line applies.
• Multitenant. Three user created pluggable databases per container without the option on Enterprise Edition. The fourth PDB is a purchase, not a configuration change.

Both allowances are release specific. Read the permitted features table for your exact version rather than repeating a number from a slide.

How far an option count actually extends

An option is licensed for the full licensed quantity of the database on the server where it runs, and only on that server. It does not automatically extend to every database in the estate.

That boundary cuts both ways in an audit.

1. It limits the claim. Partitioning used on one four Processor server is a four Processor option exposure, not an estate wide one.
2. It removes partial credit. On that server the option is licensed at the full database quantity. There is no per database or per schema licensing of an option.
3. It survives the switch off. The data dictionary keeps a first usage date. Disabling today does not erase a usage record from 2019.

Which management packs exist, and which switch themselves on?

Five packs are separately priced, not four, and two of the five enable themselves on a default install. Pack leakage is the highest volume audit finding on Oracle Database, and almost none of it is deliberate.

The five priced packs

Two named references worth keeping open while you inventory: our Diagnostics and Tuning Pack guide and the Data Masking and Subsetting page.

The prerequisite chain nobody documents

• Tuning Pack requires the Diagnostics Pack. You cannot license Tuning alone. Every Tuning finding is therefore a two pack finding at 12,500 USD per Processor.
• Diagnostics carries AWR, ASH and ADDM. Any script, dashboard or third party monitoring tool that reads those views is using the pack.
• Enterprise Manager is where both light up. The console is free. Most of the pages inside it are not.

The line item that sits outside both lists

Oracle Database Gateway products are separately licensed programs on the price list. A gateway to DB2, SQL Server, Sybase, Informix or Teradata is not an Enterprise Edition feature and not one of the options above.

It carries the same two metrics as the database, and it is counted where the gateway itself runs, which is usually a small server nobody inventoried. Look the current lines up under Oracle Database Gateways before you accept a bundled quote. A heterogeneous services connection running quietly for six years is exactly the thing nobody holds an entitlement for.

How do you count Processor and Named User Plus?

Two metrics exist on Oracle Database, and each carries its own sizing rule and its own minimum. Getting the minimum wrong is more expensive than getting the metric wrong.

The minimums table

Program	Metric	Minimum that applies
Enterprise Edition	Named User Plus	25 NUP per Processor licensed
Enterprise Edition	Processor	Cores multiplied by core factor, rounded up
Standard Edition 2	Named User Plus	10 NUP per server
Standard Edition 2	Processor	One per occupied socket, maximum two sockets
Personal Edition	Named User Plus	One per machine
Any option or pack	Follows the base	Same metric and same quantity as the database on that server

What Named User Plus actually counts

Named User Plus counts individuals and non human operated devices authorized to use the program, whether or not they are actively using it at the time. Two consequences get missed on almost every self assessment.

• Devices count. A sensor, a till, a scanner or a batch scheduler that feeds the database is a countable user in its own right.
• Multiplexing does not help. Pooling a thousand people behind twelve application connections does not produce twelve users. Oracle counts at the front of the chain.

That is why a Named User Plus position built from database accounts is almost always wrong. Build it from the population authorized to reach the data, then compare it to the floor.

The core factor in one table, and where it stops applying

Physical cores multiplied by the core factor for that exact chip, rounded up to the next whole license. The full rule set, the audit positions and the rows for older SPARC parts sit on the core factor page. The five rows below decide almost every enterprise count.

Worked count. Two sockets, ten cores per socket, Enterprise Edition, no options. On Intel that is 10 Processor licenses and 475,000 USD at list. On IBM POWER9 it is 20 licenses and 950,000 USD. Same core count, same software, twice the bill.

Rounding is always up and never to nearest, so 25 Intel cores is 12.5, which Oracle bills as 13. Check the factor against the Processor Core Factor Table version cited in your ordering document rather than the version Oracle publishes today.

The table has two hard boundaries. It never shrinks a soft partitioned count, because the count is taken on the physical host whatever the hypervisor is doing. And it does not apply in an Authorized Cloud Environment at all.

The 50 user break even, and why a metric switch cannot save more than half

Do one division. Enterprise Edition is 47,500 per Processor and 950 per Named User Plus, and 47,500 divided by 950 is 50. SE2 is 17,500 and 350, which is also 50. Partitioning is 11,500 and 230.

Every Database line on the price list sets Named User Plus at exactly one fiftieth of Processor, base and options alike. Three consequences follow, all arithmetic rather than opinion.

1. The crossover is 50 real users per Processor license. Under 50, Named User Plus is cheaper. Over 50, Processor is cheaper. Switching options on does not move it, because the options carry the same ratio.
2. The 25 NUP per Processor minimum is exactly half the Processor price. 25 multiplied by 950 is 23,750, and that is 50 percent of 47,500. Below the floor you pay the floor, and the floor is half.
3. So a metric switch on its own cannot save more than 50 percent. Not at any user count, not on any edition, not with any option stack.

A business case showing more than half is counting something else inside the same number, usually a footprint reduction or an option strip. Those savings land with or without the switch.

Worked crossover. Take the same 10 Processor Intel server.

• Processor. 10 licenses at 47,500 USD is 475,000 USD list.
• Named User Plus at the floor. 10 processors multiplied by 25 is 250 NUP, and 250 at 950 USD is 237,500 USD. Exactly half.
• Crossover headcount. 10 multiplied by 50 is 500 users, and 500 at 950 USD is 475,000 USD. The same number as the Processor line.

That gives a three band rule for any server on the estate. Under 250 named users you pay 237,500 USD however few users you have. Between 250 and 500 you pay headcount multiplied by 950. Over 500 you buy Processor.

The metric assignment nobody re runs

Most Oracle contracts permit a switch between the two metrics subject to a true up. Estates carry metric assignments set years ago against a workload that has since changed shape, and nobody re runs the arithmetic.

We run it on every Oracle Database engagement and find a switchable workload in roughly 70 percent of them. The shape repeats: a database sized at 2,000 Named User Plus that has become a back office reporting layer with 200 real users.

Price it against the bands above. On a 10 Processor server that estate holds 1,900,000 USD of list entitlement against a defensible floor of 237,500 USD. The gap is 1,662,500 USD at list before anyone mentions a discount point. The deeper treatment is in the pricing metrics CIO playbook.

How does the platform underneath change the count?

Oracle sorts virtualization into two buckets. Hard partitioning shrinks the licensed core count, soft partitioning does not, and the list of what counts as hard is short and named.

Platform posture at a glance

Technology	Oracle bucket	Count taken on
VMware vSphere	Soft partitioning	Whole physical host, and Oracle argues the cluster
Microsoft Hyper V	Soft partitioning	Whole physical host
Nutanix AHV	Soft partitioning	Whole physical host
KVM, community builds	Soft partitioning	Whole physical host
IBM LPAR, capped	Hard partitioning	Capped LPAR core count
Solaris Zones, capped	Hard partitioning	Container core count
Oracle VM Server, pinned	Hard partitioning	Pinned core count
Oracle Linux KVM, pinned	Hard partitioning	Pinned core count

The rules behind that table, the eleven technologies Oracle names, and the evidence that defends a narrower count are on the partitioning policy page and in Oracle's own partitioning policy document.

Which page to read for your platform

• VMware. Cluster scope, vSphere version effects and containment: the Oracle on VMware page and the Broadcom era VMware reference.
• Hyper V. Failover node treatment and cluster exposure: the Hyper V guide.
• Nutanix. Why AHV is not on the approved list: the Nutanix page.
• Choosing a platform. The decision itself sits on the virtualization licensing guide.

How does BYOL counting change by cloud?

Bring Your Own License does not mean the same count on every platform. The conversion rate decides whether BYOL saves money or quietly doubles the requirement.

AWS and Azure are named Authorized Cloud Environments in Oracle's cloud licensing policy. Inside them the core factor table does not apply and vCPUs are counted instead.

A 20 vCPU instance is 10 licenses whether the metal underneath is Intel or AMD. That single sentence has settled more cloud sizing arguments than any other on this page.

The four destinations worth pricing before a migration decision.

1. BYOL into OCI as a ULA exit destination. Cheapest conversion rate, highest lock in.
2. OCI with negotiated migration credits. Get them in writing before the certification date, not after.
3. AWS or Azure for the workload subset with existing platform commitments. Price the two to one vCPU rule first.
4. Third party hosted private cloud for regulated workloads. Confirm the hosting clause in your master agreement.

The workload decides the destination, and Oracle's reference architecture is rarely it. Detail sits on the cloud environments page and the AWS BYOL page.

What does an Oracle Database estate actually cost?

Both examples below price straight off the tables above. Reproduce them against your own processor count before you accept a quote from anyone, including us.

One basis for every first hand figure on this page: the Redress Oracle Database engagement file for 2024 and 2025, roughly 40 to 55 database and Java engagements across two advisory leads. Where a figure carries a range, the range is the finding.

Banking transaction system: eight Processors on Enterprise Edition

An eight Processor Enterprise Edition cluster running Partitioning, Advanced Compression, Active Data Guard and the Diagnostics Pack. Gross list lands at 800,000 USD before support. Net at a 45 percent discount is 440,000 USD, and annual support at 22 percent is 96,800 USD.

Now check that gross against the catalog. The four named lines price at 47,500 plus 11,500 plus 11,500 plus 11,500 plus 7,500, which is 89,500 USD per Processor, or 716,000 USD across eight.

The costed gross on the engagement was 800,000 USD. When a quoted gross runs above the catalog sum, the difference is a line item you have not been shown, and making Oracle name it is the cheapest hour in the whole negotiation.

Manufacturing application: Standard Edition 2, fifty named users

Standard Edition 2 on a two socket server with 50 named users. On SE2 the Processor unit is the occupied socket, so two sockets at 17,500 USD gross to 35,000 USD.

The same estate priced on Named User Plus is 50 users at 350 USD, or 17,500 USD. Net at a 35 percent discount is 11,375 USD, and annual support is 2,502 USD.

Price it both ways every time. The 10 NUP per server minimum does not bite at 50 users, but below 10 the floor sets the bill and the headcount is irrelevant. Model your own numbers in the Oracle Database licensing calculator.

What discount and support terms should you hold out for?

Discount off Enterprise Edition list runs 35 percent to 70 percent, set by volume, term length and whether you hold a credible alternative platform. Direct deals over 250,000 USD and strategic deals reach 55 percent to 65 percent.

Ask for the option discount as a separate number. The discount on the option list is usually steeper than the discount on the base database license, and no account team volunteers that.

What the option stack adds on top of the base

• One option on an EE Processor adds 21 percent at the bottom of the range. RAC One Node at 10,000 USD on a 47,500 USD base.
• And 48 percent at the top. RAC, In Memory or OLAP at 23,000 USD on the same base.
• Fully stacked, options and packs add 40 percent to 110 percent. Across the estates in the engagement file the median options share of total cost was 48 percent.

Most estates carry 15 percent to 35 percent recoverable Oracle Database spend in unused options, mismatched metrics and stranded environments, with a median of 28 percent. Compare your own position against the 2026 Oracle cost benchmarks.

Support is 22 percent of the original net, not of what you paid

Annual support is 22 percent of the original net license fee. Not 22 percent of the discounted price you paid this cycle, and not 22 percent of a reduced footprint after you retire licenses.

Options and packs carry the same 22 percent as the base database, which is why an option switched on by accident is never a one time problem. Inside most contractual caps the line then uplifts 3 percent to 4 percent a year.

Across a five year horizon that exceeds the original license fee. The support contract, not the license contract, is where lifetime cost lives. Fix the support base first and negotiate the license discount second. See the 2026 Oracle support cost page and the third party support guide.

The two clauses that make a discount survive the renewal

A first year discount that resets toward list at renewal is not a discount. It is a trial period, and two clauses are what hold it.

1. A written cap on the annual renewal uplift. In the ordering document, not in an email from the account team.
2. Option discounts tied to the database discount. Tie them so the whole stack moves together and Oracle cannot reprice the options while holding the base.

Sequence beats both clauses. Footprint reduction cut total cost 15 percent to 30 percent more than discount chasing alone across the renewals in the same file. A 70 percent discount on the wrong quantity is worse than a 50 percent discount on the right one.

Which audit findings should you expect, and how are they evidenced?

Five findings account for most of what Oracle License Management Services produces on a database estate, and every one of them is read out of the database itself rather than out of your records.

The five recurring findings

• Diagnostics Pack on every server. Enabled by default through Enterprise Manager.
• Partitioning on system tables. Default schemas use partitioning without an explicit decision.
• Advanced Compression on segments. Compression on a single segment lights the option for the whole database.
• Whole cluster counts on shared virtualization. Any cluster running an Oracle virtual machine invites a claim on every host in it.
• RAC on test environments. Test and development clusters built without an entitlement conversation.

How the evidence is produced

Option and pack usage is recorded in the data dictionary, so an audit reads it whether or not you ever tracked it. DBA_FEATURE_USAGE_STATISTICS is the view, and four columns decide the argument: NAME, FIRST_USAGE_DATE, LAST_USAGE_DATE and CURRENTLY_USED.

V$OPTION separately reports which options are linked into the binary. Oracle publishes the script it will run against you: My Oracle Support Doc ID 1317265.1 ships options_packs_usage_statistics.sql, the same file LMS asks you to execute.

Run it on every instance before Oracle does, and note the part that catches people out. The view keeps history, so turning an option off today does not clear a first usage date from 2019. Our read of the scripts is on the LMS audit script analysis page.

Why the option rule is asymmetric

An option switched on, even briefly, is treated as deployed for the licensed quantity of the database that touched it. That holds when a DBA ran a routine query. It holds when an Oracle support engineer enabled it during a patching session.

There is no partial credit and no pro rating by duration. Either the option is fully licensed on that server or you are in breach, and the remedy Oracle proposes is always a purchase.

Pack leakage is the volume finding. Diagnostics and Tuning were active on 30 to 50 percent of databases without matching entitlement across the estates we reviewed, and almost none of it was deliberate. What actually invites the letter is on the audit triggers page.

Which levers actually move the bill?

Seven moves carry every Oracle Database renewal cycle, and they work in this order. Running them out of order is the most common reason a renewal program lands nothing.

The seven moves in sequence

1. Inventory every database. Edition, version, host, partitioning posture, options enabled, packs enabled.
2. Run the option usage script. Every instance, exported and dated.
3. Disable what is not used. Diagnostics access parameter, compression segment reorganization, system table partitioning review.
4. Score the SE2 downgrade. Workloads not using EE options move to 37 percent of the EE unit price on either metric.
5. Score the cloud position. OCI BYOL at two OCPU per Processor is the cheapest conversion rate available.
6. Quote the ULA decision. An unlimited agreement against a metered position, modeled before anyone proposes it.
7. Carry the position into the procurement memo. Document it before the renewal opens, not during.

The lever on each of the four usual suspects

Where the common advice on the Oracle option catalog is wrong

The standard advice is to strip unused options at renewal. It is not wrong, it is just late, and it usually recovers a fraction of what the slide promised.

The reason is in the support policies rather than the license contract. Support is 22 percent of the original net fee for the whole order, and dropping one line from that order does not reduce the rest proportionally.

Two clauses close the door. Matching Service Levels blocks supporting part of a license set. Pricing following Reduction of Licenses or Support Level reprices what remains when you drop the rest. Both sit in the Oracle Software Technical Support Policies, both are checkable today, and neither is negotiable at the moment you want to use them.

So the option catalog is not really a renewal lever. It is a purchase order lever. The money is made by not buying the option, or by restructuring the support base at the same moment you drop it, and both of those happen before signature rather than after.

What does a ULA certification count include?

A ULA is settled in one moment, and the arithmetic in that moment is the entire deal. Certification is a counting exercise governed by the ULA amendment, not by the sales conversation that produced it.

Five clauses in that amendment decide the number, and four of the five get read for the first time in the last quarter of the term.

1. The program list. Only the programs named in the amendment are unlimited. Anything else deployed during the term is a shortfall on the certification date and it prices at list.
2. The definition of Customer. Subsidiaries are in only above the ownership threshold the amendment states. An entity acquired in year two often sits outside it.
3. The territory. Deployment outside the named territory does not certify.
4. The certification declaration. A written statement of quantities, signed by a company officer, delivered inside the window the amendment sets. Thirty days is the common shape.
5. Cloud. Whether instances in AWS or Azure count toward the certified number is a negotiated term. In the amendments we have read it is either silent or excluded. Silence is not permission.

The count itself runs on the rules above. Cores multiplied by core factor, rounded up. The 25 NUP per Processor floor on anything certified on the user metric. Options counted separately from the base at the same quantity.

That is why the hardware you run on the certification date matters more than the hardware you ran for the three years before it. The full sequence is on the ULA certification page and in the ULA Decision Framework.

The support clause that decides whether counting high is free

In a straight certification your support fee continues at the ULA support amount and the certified quantity does not change it. The extra entitlement genuinely is free on the day you sign.

In a conversion, a buyout, or any exit that generates a new order line, support is 22 percent of that new net fee, every year, with no end date. Establish which of the two your amendment produces before you decide how high to count.

The two answers point in opposite directions and no account team distinguishes between them unprompted. Across the ULA exits in the 2024 and 2025 file, certifying against realistic production footprint rather than measured maximum came out 22 to 38 percent cheaper across the support horizon that followed, median 27 percent.

40 to 55

Oracle engagements 2024 to 2025

27%

Median ULA exit saving on certified entitlement

3.1x

Median audit finding against internal estimate

Source: Redress Compliance advisory engagement file, 2024 to 2025.

What should a buyer do next?

Seven steps take an Oracle Database estate from default audit exposure to a documented, defensible position. They are ordered so that each one makes the next cheaper.

1. Inventory every instance. Edition, version, options, packs, host, platform. Include development, test, disaster recovery and anything a supplier runs for you.
2. Run the usage script on every database. Export it, date it, and store it where an auditor cannot reach it but your counsel can.
3. Reconcile against the ordering documents. Metric, quantity, territory and the exact program names, not the marketing names.
4. Strike the free lines out of your model. Spatial, Graph and Machine Learning, confirmed against the licensing manual for your release.
5. Score the two structural moves. The SE2 downgrade on workloads that use no EE feature, and the metric switch on anything under 50 users per Processor.
6. Fix the support base before the license discount. Model the third party support option even if you never take it, because the model is what moves the Oracle number.
7. Open the renewal eight months out. Anything later and the only lever left is the discount, which is the weakest one on this page.

Start with a single server if the estate is large. One correctly counted server exposes every error pattern in the rest of them.

Frequently asked questions

How many Oracle Database editions are there in 2026?

Four are in play: Enterprise Edition, Standard Edition 2, Personal Edition and Free. Enterprise Edition carries the priced option catalog and the management packs. Standard Edition 2 is capped at two sockets and 16 CPU threads with no options available at all, and Free is the resource capped release that replaced Express Edition at 23ai.

What is the list price of Oracle Enterprise Edition?

47,500 USD per Processor and 950 USD per Named User Plus at list. Standard Edition 2 is 17,500 and 350. Verify both against the current Oracle Technology Global Price List before you quote them, because Oracle revises that document without announcement and the version that matters is the one in force on your order date.

How are Oracle Database options licensed?

Each option is a separately priced program licensed at the same metric and the same quantity as the base database on the server where it runs. A 16 core Intel server on the Processor metric carries 8 Processor licenses for the base and 8 for every active option. There is no per schema, per database or partial option licensing.

Are Oracle Spatial and Graph still separately licensed?

No. Oracle moved Spatial and Graph into the base database for all editions during the 19c cycle in 2019, and Advanced Analytics became Oracle Machine Learning on the same basis. Both were previously priced options, and we still find both carried as live cost lines. Confirm against the Licensing Information manual for your release before you strike the line.

How many management packs does Oracle Database have?

Five are separately priced, not four. Diagnostics at 7,500 USD per Processor, Tuning at 5,000, Lifecycle Management at 12,000, Cloud Management at 7,500, and Data Masking and Subsetting at 23,000. The fifth sits outside most internal pack inventories, and anywhere production data is masked or subset into a test refresh, that line is in scope.

Why does the Tuning Pack cost more than its list price?

Because the Tuning Pack requires the Diagnostics Pack. You cannot license Tuning alone, so every Tuning finding is a two pack finding at 12,500 USD per Processor rather than 5,000. Budget the pair whenever anyone proposes using SQL Tuning Advisor or the tuning pages inside Enterprise Manager.

What is the Diagnostics Pack audit risk?

The Diagnostics Pack enables by default through Enterprise Manager, and AWR and ASH reports are the standard audit evidence. Oracle bills for every database server running the unlicensed pack. The control is the CONTROL_MANAGEMENT_PACK_ACCESS initialization parameter set to NONE, applied at install and evidenced by a dated change record.

When is Named User Plus cheaper than Processor?

Below 50 real users per Processor license. Oracle prices Named User Plus at exactly one fiftieth of Processor on every Database line, so 47,500 divided by 950 is 50 and 17,500 divided by 350 is 50. The 25 NUP per Processor minimum is exactly half the Processor price, which caps the saving from a metric switch alone at 50 percent.

How many licenses is a 20 core Intel server on Enterprise Edition?

Ten. Twenty physical cores multiplied by the 0.5 Intel core factor is ten licenses, and the result always rounds up, so 25 cores is 13 and not 12.5. On IBM POWER the factor is 1.0, so the same server is 20 licenses. No core factor applies in AWS or Azure, where the rule is two vCPUs to one.

Does virtualization reduce the Oracle Database license count?

Only where Oracle names the technology as hard partitioning. VMware, Hyper V, Nutanix AHV and community KVM are all soft partitioning, and the count is taken on the physical host. Capped IBM LPAR, capped Solaris Zones, Oracle VM Server and Oracle Linux KVM with pinned cores are the mainstream approved methods.

What is Oracle Database support calculated on?

22 percent of the original net license fee, not 22 percent of the price you paid this cycle and not 22 percent of a reduced footprint later. Options and packs carry the same rate as the base. Inside most contractual caps the line uplifts 3 to 4 percent a year, so across five years support exceeds the original license fee.

Can I drop an unused option and stop paying support on it?

Rarely on the terms people expect. Matching Service Levels blocks supporting part of a license set, and the repricing clause adjusts what remains when you drop the rest. Both sit in the Oracle Software Technical Support Policies. The money on options is made by not buying them, or by restructuring the support base at the same moment you drop them.

What discount should I expect off Enterprise Edition list?

35 to 70 percent, set by volume, term length and competitive pressure. Volume orders typically clear 35 percent, and direct deals over 250,000 USD reach 55 to 65 percent. Ask for the option discount separately, because it is usually steeper than the base database discount and tying the two together is what makes the position survive the next renewal.

How does Redress engage on an Oracle Database review?

Redress runs Oracle Database advisory inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program and the Software Spend Assessment.

The engagement covers the option usage extract, the audit posture, the SE2 and metric scores, the cloud position and the procurement memo. Every engagement is led buyer side, with no Oracle reseller margin anywhere in the room.

Continue with the Oracle hub, the Oracle services page, the Oracle licensing guide for the wider portfolio, our benchmarking approach, the about us page, our locations, and the contact page.