Standard Edition One stopped selling years ago, yet it still sits in production estates and still draws audits. Here is what the metric was, what changed with SE2, and how to migrate without overpaying.
Oracle Standard Edition One is retired from the price list but remains fully auditable wherever it still runs, and the move to Standard Edition 2 reshaped both the socket cap and the price.
Standard Edition One was a socket based edition aimed at smaller servers. It could be licensed on systems with a maximum of 2 processor sockets, and it carried its own Named User Plus minimum. The rules are set out in the Oracle Database Licensing Information document, which remains the controlling reference even for retired editions.
Two licensing facts mattered most. The metric counted sockets, not cores, so the core factor table did not apply. And the Named User Plus floor was lower than Enterprise Edition, which made SE1 attractive for departmental systems.
From Oracle Database 12.1.0.2, Oracle retired both Standard Edition and Standard Edition One and replaced them with a single edition, Oracle Database Standard Edition 2. The change was not cosmetic. It altered the socket ceiling, added a thread cap, and reset the Named User Plus minimum.
The headline shift is the 16 thread cap. SE2 will run on a 2 socket server, but it limits any single database instance to 16 CPU threads. On dense modern processors that is a real performance ceiling, not a paperwork detail.
SE1 compared with SE2
| Attribute | Standard Edition One | Standard Edition 2 |
|---|---|---|
| Socket maximum | 2 sockets | 2 sockets |
| Thread cap | None | 16 threads per instance |
| Named User Plus minimum | 5 per socket | 10 per server |
| Status | End of sale | Current edition |
A modern 2 socket server can present dozens of threads. SE2 ignores the surplus. Buyers who size on raw core counts overestimate the performance they will actually get, and sometimes overbuy Enterprise Edition to compensate when right sizing SE2 would have served.
White Paper ยท Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
Oracle audits the estate it finds running, not the estate you bought. Under the Oracle Master Agreement, the right to verify deployment does not lapse because an edition left the price list. Legacy SE1 on an oversized server is one of the most common findings in a database review.
Support is the other pressure point. Under the Oracle Lifetime Support Policy, older database releases fall out of Premier and Extended Support, which pushes buyers toward an upgrade that is also a license event.
Treat the migration as a contract action, not an infrastructure task. Confirm what you are entitled to, map it to SE2 rules, and only then schedule the technical upgrade. The order protects you.
The Oracle Technology Price List and the Oracle Software Investment Guide together give you the list price and discount context you need to test any Oracle migration quote. Bring both to the table.
The standard reseller advice is that retired editions are low risk because Oracle no longer sells them, so a quiet upgrade to SE2 settles everything. We disagree. In a clear majority of the legacy Standard Edition estates Fredrik Filipsson reviewed, the upgrade itself created the exposure, because infrastructure teams moved binaries without checking the socket cap, the thread limit, or the changed Named User Plus floor. The buyer side move is to freeze every SE1 upgrade until entitlement is confirmed in writing, then migrate deliberately. An edition leaving the price list narrows your options, it does not narrow Oracle's audit rights.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
An edition leaving the price list narrows your options. It does not narrow Oracle's right to audit what you run.
Standard Edition One is end of sale and is no longer current. It still runs in production, but newer database releases use Standard Edition 2, and older releases fall out of Premier Support under the Oracle Lifetime Support Policy.
Standard Edition 2 replaced both Standard Edition and Standard Edition One from Oracle Database 12.1.0.2. SE2 keeps the 2 socket limit but adds a 16 thread per instance cap and a revised Named User Plus minimum.
Yes, you can still run SE1 binaries you are entitled to, but you remain fully auditable. The risk is running it on oversized hardware or upgrading to SE2 without a contract review.
No. Standard editions are licensed by socket, not by core, so the Oracle Processor Core Factor Table does not apply. That table governs Enterprise Edition processor licensing.
Standard Edition 2 may be licensed on servers with a maximum of 2 processor sockets, and any single instance is capped at 16 CPU threads regardless of how many cores the server presents.
It can be. Moving onto an SE2 binary changes the edition you are running and the rules that apply, so it should be confirmed against your entitlement before the technical upgrade, not after.
Oracle scripts and review tooling read the installed edition and the host configuration. SE1 on a server above the socket cap, or SE1 cloned across a virtual cluster, are common findings.
Not by default. Many SE1 workloads fit within the SE2 thread cap. Moving to Enterprise Edition multiplies cost through per core licensing and options, so confirm the workload actually needs it first.
Oracle ULA exit moves, Java audit defense posture, certification framework, and the buyer side moves across the Oracle Database, Java, and EBS estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Confirm entitlement before the upgrade, never after. The order is the whole game.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
Short, buyer side notes on Oracle audits, editions, and renewals. No vendor spin.
