Oracle Standard Edition One (SE1)

Oracle Standard Edition One was a legacy SKU for small server deployments. Oracle ended new sales in 2015 and replaced the product with Standard Edition Two. Existing SE1 deployments stay on the contract, on the support stream, and inside the audit scope.

The SE1 metric is per processor with a two socket server cap. The Named User Plus floor is five users per server. Both are tighter than the equivalent rules on SE2 and EE.

Read this alongside the Oracle knowledge hub, the SE2 vs EE guide, the EE options article, the ULA framework, and the Vendor Shield subscription.

Key Takeaways

What a DBA lead and procurement carry on legacy SE1 estates

End of sale 2015. No new SE1 license purchases since the SE2 release.
Two socket cap. SE1 restricted to servers with two sockets or fewer.
Five NUP per server floor. Lower than the 25 per processor floor on EE.
SE1 still on the support stream. Customer Support Identifier carries SE1 entitlement until canceled.
Migration is mandatory at refresh. Hardware refresh past two sockets forces a move to SE2 or EE.
Options not licensable on SE1. Partitioning, RAC, and most EE options never sold on SE1.
Audit posture is moderate. Common findings are over the socket cap and option misuse.

End of sale history and what changed

Oracle announced the end of sale of Standard Edition and Standard Edition One on 1 September 2015. Standard Edition Two replaced both SKUs on the price list. The migration window for active deployments ran into 2016 and 2017.

SKU history table on Standard Edition

SKU	Active period	Server cap	List USD per CPU
Standard Edition One	Until September 2015	Two sockets	5,800
Standard Edition	Until September 2015	Four sockets	17,500
Standard Edition Two	September 2015 onward	Two sockets, sixteen threads	17,500
Standard Edition Two refresh	2019 onward	Two sockets, sixteen threads	17,500

What changed at the SE2 transition

Two socket cap retained. SE2 carried the SE1 socket cap forward.
Sixteen thread cap introduced. SE2 added a thread cap of sixteen on the database engine.
RAC limited. Standard Edition Two retained RAC up to a defined cluster size until 2020, when Oracle removed RAC on SE2.
NUP floor consistent. Five users per server retained.
List price aligned to SE level. Lower SE1 price point retired.

SE1 metric and socket cap rules

SE1 is licensed per processor or per Named User Plus, with restrictive caps that differentiate it from Enterprise Edition. The metric rules are mechanical and remain enforceable today.

The four governing rules on SE1

Two socket server cap. SE1 cannot run on servers with more than two physical processor sockets.
Per processor counts sockets. The Oracle core factor table does not apply to SE1. The metric is whole sockets.
Named User Plus minimum. Five users per server, regardless of named user count.
Cluster cap. RAC on SE1 capped at a defined cluster size, removed entirely on SE2 in 2020.

SE1 per server license footprint

Server class	Sockets	SE1 licenses required	NUP minimum
Single socket pizza box	1	1 processor	5 NUP
Dual socket 1U server	2	2 processors	10 NUP
Four socket server	4	SE1 not licensable	SE1 not licensable
Eight socket server	8	SE1 not licensable	SE1 not licensable

Audit traps on legacy SE1 estates

Oracle License Management Services regularly audits SE1 deployments. The legacy SKU is well documented, the metric is mechanical, and the audit math is fast.

Five common SE1 audit findings

Hardware refresh past two sockets. Server migrated to a four socket box, SE1 license no longer valid.
EE option enabled in error. Partitioning, Diagnostics Pack, or Tuning Pack feature touched on a SE1 install.
RAC cluster exceeds cap. RAC nodes added beyond the SE1 cluster cap, full RAC license obligation triggered.
VMware soft partitioning. SE1 virtual machine on a vSphere cluster, every host on the vMotion scope in license scope.
Five NUP floor missed. Sub five user deployment, full NUP floor still required per server.

Buyer side defense moves on SE1

Inventory every SE1 install. Server identity, socket count, hardware refresh history.
Confirm no EE options touched. Run DBA_FEATURE_USAGE_STATISTICS, screen for option features.
Document the entitlement. Customer Support Identifier, active support, processor and NUP count.
Plan the migration window. SE1 to SE2 or SE1 to EE, hardware refresh aligned to the contract.
Pre price the gap. Calculate clean licensing before Oracle quotes a settlement.

The forgotten SE1 install

SE1 was the SKU for small departmental databases. A decade after end of sale, many enterprises still run SE1 on a legacy server in a regional office, with no active DBA ownership. The audit reaches the forgotten install. The settlement quote treats every unlicensed feature as a full EE option obligation.

Migration paths off SE1

Three migration paths cover most SE1 estates. The right path depends on workload size, feature usage, and the broader Oracle commitment.

The three migration paths

SE1 to SE2. Like for like edition swap, same socket cap, sixteen thread cap. Use when workload fits SE2.
SE1 to EE. Upgrade for workloads that exceed sixteen threads, need RAC, or need EE options. Higher per processor cost.
SE1 to Autonomous Database or OCI. Cloud migration with consumption based pricing. Use when on premises hardware refresh is unavoidable.

Migration path comparison matrix

Path	Effort	Per CPU rate	When to choose
SE1 to SE2	Low	17,500 USD	Workload fits inside 16 threads
SE1 to EE	Medium	47,500 USD	Need EE options or larger compute
SE1 to Autonomous Database	Medium to High	Per OCPU per hour	Move to cloud, retire on premises
SE1 to PostgreSQL or open source	High	No Oracle license	Exit Oracle entirely

Discount and remediation benchmarks

SE1 migration discount sits inside the broader Oracle commercial conversation. The migration credit, the support credit, and the cloud move credit all play into the math.

Indicative buyer side discount ranges on migration

Scenario	Discount range off list	Notes
SE1 to SE2 swap	40% to 65%	Like for like, leverage on volume
SE1 to EE upgrade	50% to 70%	EE base discount applies, options separate
SE1 to OCI BYOL	BYOL credit	Existing license carries to OCI compute
SE1 audit settlement	15% to 40%	Audit posture punishes discount

What to do next

The seven step buyer side checklist puts a SE1 estate on a clean licensing footing before the next Oracle conversation, audit, or hardware refresh cycle.

Inventory every SE1 install. Server identity, socket count, version, region, hardware refresh history.
Reconcile the entitlement. Customer Support Identifier, active support, processor and NUP count.
Run DBA_FEATURE_USAGE_STATISTICS. Confirm no EE options touched, screen for RAC, ASM, or option features.
Map the hardware roadmap. Identify SE1 servers approaching refresh past the two socket cap.
Choose the migration path. SE2, EE, OCI, or exit Oracle entirely.
Pre price the gap. Use the migration discount benchmarks above.
Open the Oracle conversation. Document driven, with a multi year scenario in hand.

Frequently asked questions

Is Oracle Standard Edition One still available?

No. Oracle ended new sales of Standard Edition One on 1 September 2015. The product was replaced on the price list by Standard Edition Two. Existing SE1 deployments remain on the customer support stream and stay on the contract until the support is canceled. New license purchases are not possible.

What is the socket cap on SE1?

SE1 is restricted to servers with two physical processor sockets or fewer. The third socket on a server immediately makes the SE1 license invalid for that server. The Oracle core factor table does not apply to SE1, the metric counts whole sockets on the server.

What is the Named User Plus floor on SE1?

Five Named User Plus per server is the minimum on SE1. The floor applies regardless of the actual named user count. A two user SE1 install on a single socket server still requires five NUP licenses to remain compliant. The floor is lower than the 25 per processor minimum on Enterprise Edition.

Can SE1 use EE options like Partitioning?

No. Standard Edition One does not license Enterprise Edition options. Partitioning, Diagnostics Pack, Tuning Pack, RAC at scale, Advanced Compression, and Advanced Security are not available on SE1. Touching any of those features on a SE1 install creates a full EE option obligation on the audit.

What is the best migration path off SE1?

The right path depends on workload size and feature usage. SE1 to SE2 is the like for like swap when the workload fits inside sixteen threads. SE1 to EE is the upgrade path for larger workloads or EE option requirements. SE1 to OCI Autonomous Database is the cloud move when on premises hardware refresh is unavoidable. SE1 to open source is the Oracle exit path.

How does Redress engage on legacy SE1 estates?

Redress runs the SE1 inventory, the option usage scan, the migration path analysis, and the renewal positioning inside the Vendor Shield subscription and the Renewal Program. Every engagement is led by a former Oracle commercial executive on the buyer side, with no Oracle sales conflict on the table.

How Redress engages on Oracle legacy SKU strategy

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

Read the related benchmarking page, the about us page, the locations page, and the contact page.

Vendor Advisory

Cloud & Emerging

Programs

Assessments

Research

Knowledge Hubs

Assessment Tools

Oracle SE1. End of sale, still in scope.