Oracle SE1, end of sale was never end of entitlement
Standard Edition One is retired from the price list but remains fully auditable wherever it still runs: a perpetual SE1 license still covers the releases it was granted for, on servers with a maximum capacity of two sockets, and every forward path runs through Standard Edition 2, a toll booth Oracle controls. The strategy starts by separating the operational risk from the compliance position, because they are not the same thing.
Prepared by Redress Compliance · August 7, 2026 · Oracle advisory. Based on 30 to 40 Oracle engagements reviewed 2024 to 2025.
Executive summary
SE1 hides in half the modernized estates.
Legacy Standard Edition One appeared in about half of the database estates that believed they were fully modernized, and the findings clustered three ways: stranded instances on hardware above the socket capacity rule, putting 20 to 40 percent of the footprint in question.
SE2 binaries applied by infrastructure teams with no license check, converting a clean estate into a finding overnight, because the upgrade is the license event; and Named User Plus counts left at the old SE1 floor, understating the SE2 requirement on every converted server.
The capacity rule reads the chassis, not the chips. SE1 licensed per occupied socket with no core arithmetic, on servers whose maximum capacity could not exceed two sockets: two chips in a four socket board is still a breach, and a multi chip module counts each chip as its own socket.
Under virtualization the rule compounds, a small SE1 guest inherits the socket capacity question of every host it can reach, live migration multiplies the exposure across the cluster, and template clones keep retired images alive for years.
The floors moved and the conversion has a toll.
SE1 carried a flat 5 Named User Plus minimum at $5,800 per socket; SE2 requires 10 NUP per server, throttles every instance to 16 CPU threads, and Oracle's published migration guidance put roughly a 20 percent uplift on SE1 support streams at conversion.
On a two server estate the minimum user spend doubles before an additional person logs in, and every supported release from 12.1.0.2 onward, including 19c and 23ai, is SE2 only.
What the entitlement still covers is real and bounded.
The granted releases, 10g, 11g, and 12.1.0.1, indefinitely; redeployment onto any replacement server satisfying the capacity rule; the ten day unlicensed failover allowance; and survival without support, though patches and service requests end with it.
Sustaining Support keeps existing patches and documentation forever but adds no new security fixes or certifications, which is an operational risk position, not a compliance gap, and Oracle's renewal pressure depends on conflating the two.
The SE1 timeline, and what each date means for a holder
| Date | The event | What it means for a holder |
|---|---|---|
| 2004 | SE1 joins the price list in the 10g era | A $5,800 per socket edition builds a wide departmental base |
| September 2015 | Standard Edition 2 announced with 12.1.0.2 | SE1 and SE leave the price list for good |
| 2016 | Error correction ends for SE1 on 12.1.0.1 | The last SE1 release stops receiving patches |
| 2019 onward | 19c ships as the long term release, SE2 only | Every supported upgrade path requires conversion |
| 2026 | All SE1 releases sit in Sustaining Support | No new fixes or certifications, and audits continue |
End of sale ended purchases, not transfers or renewals. You can keep running what you own for as long as it serves, renew existing support, and transfer within your entity, subject to the assignment clause, which is exactly where legacy entitlements quietly get lost in corporate restructuring.
Confirm any merger or carve out against that clause before assuming the SE1 paper traveled with the deployment.
What SE2 changed, floor by floor
| Dimension | SE1 | Standard Edition 2 |
|---|---|---|
| List per socket | $5,800 | $17,500 |
| The NUP floor | A flat 5, total | 10 per server |
| The thread cap | None | 16 CPU threads per instance |
| The releases | 10g, 11g, 12.1.0.1 | 12.1.0.2 through 19c and 23ai |
| The conversion toll | Roughly 20 percent support uplift at migration |
The Standard Edition 2 licensing brief
The socket editions end to end: the capacity rules, the conversion mechanics, the virtualization boundaries, and the SE2 estate run correctly.
Get the white paper →The virtualization exposure, and the cheap control
The socket editions license against physical hardware, so a virtual machine inherits the socket capacity question of every host it can run on: an SE1 guest on a host with capacity above two sockets fails the rule regardless of the virtual hardware assigned.
Live migration raises the question for every host the image could reach, and template libraries and DR copies keep old SE1 images alive years after production retired.
The control is unglamorous and nearly free, a small dedicated host pair for legacy socket edition guests, mobility pinned and documented, and in our estates it removed the single largest SE1 exposure at close to zero infrastructure cost.
The frozen estate with a fixed retirement date is also the textbook third party support case, the releases receive no new Oracle patches anyway, with the one caveat that leaving Oracle support forfeits upgrade rights, so never do it on an estate still intended for SE2 conversion.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across SE1 and SE2 estates, 2024 to 2025
Across roughly 30 to 40 Oracle engagements Fredrik Filipsson reviewed between 2024 and 2025, legacy Standard Edition One appeared in about half of the database estates that believed they were fully modernized:
SE2 binaries applied by infrastructure teams with no license check, because the patch is the license event.
Left at SE1's flat five, understating the ten per server SE2 requirement on every converted box.
The leverage of an SE1 holder in 2026 is the separation nobody makes: Sustaining Support is an operational risk Oracle amplifies at every renewal, not a compliance gap, and the holder who distinguishes the two chooses between the frozen estate on third party support funding its own retirement.
The deliberate SE2 conversion priced with the 20 percent toll and the new floors in view, or the platform exit entirely, benchmarked in the PostgreSQL comparison.
The SE2 side of the fence, the socket counting and the crossover arithmetic, sits in the SE2 licensing guide and the edition comparison, priced against the technology price list.
Your first five moves
- Sweep for SE1 instances, because half the modernized estates still carried them, on hardware and in template libraries alike.
- Check every SE1 host against the capacity rule, chassis maximum and not populated sockets, including every host a virtualized guest can reach.
- Gate binary upgrades behind license checks, since one SE2 patch applied by an infrastructure team converts the estate.
- Re count NUP under the SE2 floors on every converted server, ten per server against the old flat five.
- Choose the path deliberately: frozen on third party support, converted with the toll priced, or exited. The Oracle practice runs the decision with you.
Frequently asked questions
Is Oracle SE1 still legal to run?
Yes: end of sale ended new purchases, not entitlements, and a perpetual SE1 license still covers Oracle Database 10g, 11g, and 12.1.0.1 on servers with a maximum capacity of two sockets, indefinitely, with redeployment rights onto compliant replacement hardware.
It also remains fully auditable, and it appeared in half the estates that believed they were modernized.
What does the SE1 two socket rule actually require?
Maximum chassis capacity of two sockets, not two populated sockets: two chips in a four socket board is a breach, and a multi chip module counts each chip as its own socket.
Under virtualization the rule reads every host the guest can reach, which is why live migration across a shared cluster is the recurring SE1 audit story.
What does converting SE1 to SE2 cost?
Oracle's published migration guidance applied roughly a 20 percent uplift to SE1 support streams at conversion, and the floors move with it: the flat five NUP minimum becomes ten per server, and every instance throttles to sixteen CPU threads.
On multi server estates the minimum user spend multiplies before a single additional person logs in.
Can SE1 keep running without Oracle support?
Yes: the perpetual license survives dropping support, though patch access and service requests end with it, and all SE1 releases sit in Sustaining Support anyway, which adds no new fixes or certifications.
A frozen estate with a fixed retirement date is the textbook third party support case, with the caveat that leaving forfeits the upgrade rights an SE2 conversion would need.
Why do SE2 patches create SE1 compliance findings?
Because the upgrade is the license event: applying an SE2 binary to an SE1 licensed system changes the compliance position instantly, and infrastructure teams patching without a license check converted clean estates into findings overnight in our reviews.
Entitlement comes first, binaries second, enforced by gating upgrades behind the license question.
Is Sustaining Support a compliance problem?
No, and the distinction is the SE1 holder's leverage: Sustaining Support is an operational risk position, no new security fixes or certifications, which Oracle amplifies in renewal conversations, but it is not a compliance gap.
Separating the two lets the holder choose deliberately between freezing, converting with the toll priced, or exiting the platform.
