Oracle Standard Edition 2 limitations and licensing. Sockets, threads, users and cost.

SE2 runs only on servers built for two sockets, caps each database at sixteen threads and lists at $17,500 per occupied socket. Enterprise Edition lists at $47,500 per Processor times cores, so measure option usage, threads and sockets before you choose.

What are the Oracle Standard Edition 2 limitations?

Standard Edition 2 has four limits. It runs only on servers with a maximum capacity of two sockets, each database uses at most sixteen CPU threads, Named User Plus licensing carries a minimum of ten users per server, and no Enterprise Edition option or feature may be used.

In return, SE2 lists at $17,500 per occupied socket and ignores cores entirely. Enterprise Edition lists at $47,500 per Processor, where a Processor means cores multiplied by the core factor. That price gap drives every edition decision we review, and Oracle account teams rarely open with it.

Which of the four limits does the software enforce?

Only the thread cap. The database holds itself to sixteen threads, so crossing that line costs performance and never money. The other three surface when someone reads the contract against your servers, usually an auditor.

How does Oracle count sockets for SE2?

Two tests apply. Eligibility follows the server's maximum socket capacity, so the machine must be built for no more than two sockets. The license count follows occupied sockets, so a two socket server with one processor fitted needs one SE2 Processor license.

• Capacity decides eligibility. A four socket chassis does not qualify even with two chips fitted, which makes the chassis model a license decision.
• Blades count individually. Each blade is its own server, so eight two socket blades in one chassis are eight qualifying servers.
• Cores are free. The core factor never touches SE2. On core count alone, two sockets of 64 core AMD EPYC license the same as two sockets of 8 core Xeon.
• Virtual machines create no sockets. Oracle licenses the physical server, so a two socket virtual machine on a four socket host does not qualify the host.
• Hard partitioning works only inside the limit. SE2 may run on one socket of a two socket server under an approved hard partitioning technology, never on a slice of a larger server.

Does a multi chip processor count as one socket?

Not necessarily. Oracle's price list counts each chip in a multi chip module as one occupied socket for Standard Edition products, and its documents do not say which current processors it treats that way. Before you buy chiplet based hardware such as AMD EPYC for SE2, get written confirmation that your model counts as one socket per package.

How does a hardware refresh break SE2 compliance?

A refresh changes the server under the database, and the database never notices. Move an SE2 workload onto a four socket model and a compliant server becomes an Enterprise Edition liability with no software change at all.

The bill is the whole server at EE list, cores times core factor, backdated to install, plus back support. In two of every three SE2 environments we reviewed, at least one server had grown past two occupied sockets during a hardware refresh.

How do the limits translate to AWS, Azure and Google Cloud?

Under Oracle's Authorized Cloud Environment policy, SE2 is allowed on instances of up to 8 vCPU, and every four vCPU count as one socket, rounded up. The core factor does not apply in authorized cloud.

• Providers. The policy long named AWS and Azure; Oracle has since added Google Cloud under the same SE2 rules.
• Sizing. An instance of 4 vCPU or fewer needs one SE2 Processor license, an 8 vCPU instance needs two, and anything larger is ineligible.
• Dedicated hosts. EC2 Dedicated Hosts expose the host's physical sockets, which supports a count based on real hardware in place of the vCPU conversion. Agree that method with Oracle in writing first.

What does the 16 thread limit mean in practice?

SE2 caps each database at sixteen CPU threads at any time. With hyperthreading on, a two socket server with sixteen cores presents 32 threads, and one SE2 database uses sixteen of them. You buy roughly half the machine's execution capacity for about a tenth of the Enterprise Edition price.

The cap applies per database, and Oracle allows as many SE2 databases on a server as it can support, each with its own sixteen thread cap.

How do you tell whether the thread cap is hurting?

The cap shows up as throughput that stops scaling, usually first at period end batch, and never as an audit finding. In Statspack reports, sustained waits on resmgr:cpu quantum are the usual sign a database is queuing for its sixteen threads.

Profile the workload before you promise a step down. On an Enterprise Edition database, AWR and ASH need the Diagnostics Pack, so use Statspack or sar if you do not own it. Measure peak CPU demand across a full month end close.

How much cheaper is SE2 than Enterprise Edition?

At list, SE2 costs 90.8 percent less than Enterprise Edition on a typical two socket, sixteen core Intel server. On databases that qualified and moved, license and support cost fell 50 to 70 percent over five years, because the Enterprise Edition being replaced usually carried a discount the SE2 purchase will not.

Why is the realized saving smaller than the list gap?

You already own the Enterprise Edition licenses, so the EE path costs support only, charged at 22 percent of the net price you paid. Say, as a hypothetical, the EE licenses on this server were bought at 60 percent off list.

1. Enterprise Edition: $152,000 net, so support is $33,440 a year, or $167,200 over five years.
2. SE2 at 10 percent off list: $31,500, plus $6,930 a year in support, or $66,150 over five years.
3. The saving is $101,050, about 60 percent.

The deeper your EE discount, the smaller the saving. Repricing can shrink it further: when you terminate some licenses on an order, Oracle reprices support on the rest at list less the standard discount, up to the fees you paid before. Price the support repricing before you give notice.

How do Named User Plus minimums work on SE2?

SE2 Named User Plus lists at $350 with a minimum of ten users per server, so a server licensed by user costs at least $3,500. On two sockets, 100 named users cost the same as two Processor licenses at $35,000.

In our reviews, misapplied minimums over licensed small databases by 10 to 30 percent. The errors to check for:

• Using the EE minimum. Enterprise Edition requires 25 Named User Plus per Processor. SE2 has no per Processor minimum.
• Applying the floor per database. Three small databases on one server share a single ten user floor.
• Missing multiplexed users. People who reach the database through an application tier still count, as the guide to multiplexing and front end users explains.

The NUP versus Processor crossover calculator runs the comparison for other server sizes.

What do you lose when you move from Enterprise Edition to SE2?

You lose every priced option and a set of built in Enterprise Edition features, so qualification is functional before it is financial. These most often block a step down:

• Parallel query and parallel DML, which batch and reporting jobs often use without anyone having chosen them.
• Bitmap indexes, Data Guard, Flashback Database and materialized view query rewrite.
• Partitioning, the Diagnostics and Tuning Packs and every other priced option.

Two features moved the other way: Oracle folded Spatial and Graph and Oracle Machine Learning into the core database, SE2 included, so their usage does not block a move. On SE2 they run serially, because SE2 has no parallel operations. The full comparison is in the EE versus SE guide.

What replaced RAC on SE2?

RAC was desupported on SE2 from Oracle Database 19c, with no option to restore it. Standard Edition High Availability, included from Release Update 19.7, is the active passive replacement, failing a single instance between two nodes on shared storage.

Ask whether the old cluster bought resilience or scale. SEHA covers resilience at SE2 prices, with the passive node under the ten day failover rule. A cluster built for scale needs Enterprise Edition. The SE2 RAC at 19c analysis covers the migration.

What have we seen in Oracle edition reviews in 2024 and 2025?

Our file for 2024 and 2025 holds 20 to 28 Oracle reviews I led where edition choice was in scope. The repeating finding is that much of the Enterprise Edition footprint never used anything Enterprise Edition does; for databases that did use it, EE was rarely overpriced.

• Unused Enterprise Edition. 40 to 60 percent of departmental EE databases returned no option usage at all in the feature usage statistics.
• Refresh breaches. The socket breach after a hardware refresh was the expensive finding, and a census after each hardware event was the cheapest control against it.
• Small databases over licensed. Named User Plus minimums applied the wrong way inflated the cost of small databases, as the section on user minimums shows.
• Savings set by the old discount. Where databases qualified and moved, the discount held on Enterprise Edition decided how much of the list gap turned into real money.

Is SE2 low risk because the software enforces its limits?

A common view among DBAs is that SE2 is the safe edition because it polices itself. We disagree. Only the thread cap is enforced in software, and the costly SE2 findings in our reviews came from servers refreshed onto a larger chassis and user floors counted wrongly.

An Enterprise Edition feature recorded on an SE2 server carries the same kind of exposure. The better course is to treat any hardware change on an SE2 server as a license event, with the change ticket asking for socket capacity before the order is placed.

Keep Enterprise Edition where its features earn the price, and step down where the usage record shows they never did.

How do you check your own SE2 and EE position?

Three measurements settle the edition question: option usage, thread profile and socket count. Take them every year and after any hardware change.

• Option usage. Query DBA_FEATURE_USAGE_STATISTICS, or run Oracle's options_packs_usage_statistics.sql from My Oracle Support Doc ID 1317265.1. The method is in the Oracle licensing guide, and the feature usage report guide covers running it before Oracle does.
• Edition installed. Query v$version to see whether EE or SE2 binaries are running, whatever the order form says.
• Sockets. On Linux, dmidecode lists every processor socket on the board and marks each populated or unpopulated. The model's specification sheet confirms maximum capacity.
• Threads. Statspack snapshots or sar across a month end.

What will Oracle's account team say about a move to SE2?

Expect resistance, because a step down cuts Oracle's support revenue for years. These are the lines we hear most.

What contract terms should you ask for when stepping down?

• A written repricing statement. Oracle's support figure for the licenses you keep on each order, so the saving is fixed before notice goes in.
• A price hold on further SE2 licenses. If more databases will step down later, fix the SE2 discount for those purchases now so each later move is priced on the same terms.
• A cap on support increases. Ask for a limit on the annual uplift for the new SE2 support lines, since a small order has little weight at later renewals.
• Processor confirmation. For chiplet processors, written confirmation of one occupied socket per package.
• Cloud counting method. For EC2 Dedicated Hosts, written agreement to count physical sockets.

The negotiation approach for any step down is set out in the database licensing reference.

What to do next

1. This quarter. Pull the feature usage statistics on every departmental Enterprise Edition database and list those with no option usage.
2. Before any hardware order. Add a socket capacity check to the change process for every SE2 server, blades included.
3. Before promising a step down. Profile threads across a full month end with Statspack or sar.
4. At the next license review. Check the NUP floor per server and whether user or Processor licensing is cheaper.
5. Six months before support renewal. Run five year cost on both paths, including repricing of what you keep.
6. If you want help. The Oracle practice runs the edition review with you.

Frequently asked questions