Oracle Standard Edition One (SE1) Licensing: Rules, End of Life and Migration Path

What Was Oracle Standard Edition One?

Oracle Standard Edition One (SE1) was introduced to provide a lower-cost Oracle database option for small and mid-size deployments. It sat below Standard Edition (SE) in Oracle's product hierarchy and was licensed on a Named User Plus or Processor basis, with a restriction that the server on which it ran could have a maximum of two sockets.

SE1 included the core Oracle database engine with a subset of features — no Real Application Clusters (RAC), no partitioning, no advanced security, and no Data Guard replication. For workloads that required only a reliable relational database on modest hardware, SE1 offered a materially lower cost than Standard Edition or Enterprise Edition.

SE1 Licensing Metrics

SE1 was available under two licensing metrics. The Named User Plus (NUP) metric charged per individual user with minimum user counts applying per server. The Processor metric charged per CPU socket (not per core), capped at the two-socket hardware limit. SE1 Processor licensing was priced at $5,800 per socket at Oracle list price, making a fully licensed two-socket server $11,600 — significantly below SE2's $17,500 per socket at list pricing.

Key SE1 Restrictions

• Maximum two sockets — SE1 could not be deployed on servers with more than two physical CPU sockets
• No Real Application Clusters — clustering for high availability was not available under SE1
• No Enterprise Edition options — partitioning, advanced security, in-memory, and other EE add-ons were not licensable with SE1
• Single-instance only — SE1 supported only single-instance database deployments
• Limited to specific database releases — SE1 was available for Oracle 9i through Oracle 12c Release 1 (12.1)

When and Why SE1 Was Discontinued

Oracle discontinued SE1 for new purchases effective December 1, 2015. This was part of Oracle's product consolidation that also eliminated Standard Edition (SE) at the same time, leaving Oracle Standard Edition 2 (SE2) as the sole sub-Enterprise Edition database option.

Oracle's stated rationale was simplification of the product line. The practical effect was to push customers onto SE2, which carried a higher per-socket price ($17,500 versus SE1's $5,800 per socket at list) and introduced new licensing constraints including the 16-database-thread limit and the eventual elimination of RAC support in Oracle 19c.

Support Lifecycle for SE1

Premier Support for Oracle Database SE1 ended on September 1, 2016 — less than a year after new purchases were discontinued. This means SE1 has been in Sustaining Support for nearly a decade. Sustaining Support provides access to existing patches, fixes, and upgrade scripts, but does not include new security patches, new fix releases, or certification with new operating system versions.

The practical risk of running SE1 on Sustaining Support in 2026 is significant. New security vulnerabilities discovered since September 2016 have not been patched for SE1. An organisation running SE1 today is operating software that Oracle no longer secures.

SE1 vs SE2: The Core Differences

When Oracle replaced SE and SE1 with SE2, several licensing parameters changed. Understanding these differences is essential for organisations planning migration.

Price

SE1 Processor licensing was $5,800 per socket at Oracle list. SE2 Processor licensing is $17,500 per socket at Oracle list — approximately three times more expensive per socket. However, when migrating existing SE1 licences to SE2, Oracle has historically offered zero-cost licence transitions for customers with active support contracts. The cost impact of migration is primarily the uplift in annual support fees: SE2 support at 22% of the higher licence cost represents a material increase over SE1 support.

Thread Limit

SE2 introduced a 16-database-thread limit per database instance that did not exist in SE1. On modern multi-core servers, this limit can constrain performance. A server with two sockets and 16 cores per socket — a common configuration in 2026 — provides 32 physical cores, but SE2 will use only 16 threads for database processing regardless of available hardware capacity.

RAC Support

SE1 never supported RAC. SE2 introduced limited RAC support (up to two nodes with Standard Edition High Availability) in early versions, but Oracle removed RAC support entirely from SE2 in Oracle Database 19c (2019). Organisations running SE2 with RAC configurations on pre-19c versions who upgrade to 19c will lose their HA topology unless they license Enterprise Edition with the RAC option.

Named User Plus Minimums

SE1 required a minimum of 5 Named User Plus licences per server. SE2 increased this minimum to 10 Named User Plus licences per server. For small deployments with fewer than 10 actual users, this minimum can make SE2 NUP licensing more expensive than the Processor metric.

Migration Options from SE1

Organisations still running Oracle Database SE1 have three principal migration paths. The right choice depends on workload requirements, risk tolerance, and long-term platform strategy.

Option 1 — Migrate to Oracle SE2

For organisations that need to remain on Oracle Database and whose workloads fit within SE2's constraints (two-socket server, 16-thread limit, no RAC, no EE options), SE2 is the natural successor. Oracle has offered zero-cost licence transitions from SE1 to SE2 for customers with active support. The migration itself is technically straightforward — an in-place upgrade or a fresh installation with data migration using Data Pump export and import.

The key consideration is the support cost uplift. SE2 support is 22% of licence cost annually, and the SE2 licence value is significantly higher than SE1 even at the zero-cost transition value Oracle assigns. Annual support for SE2 increases by 8% per year under Oracle's standard renewal terms.

Option 2 — Upgrade to Oracle Enterprise Edition

If the workload requires capabilities that SE2 cannot deliver — RAC for high availability, partitioning for performance, or advanced security — upgrading to Enterprise Edition may be necessary. EE Processor licensing is $47,500 per core at Oracle list (subject to core factor), and EE options such as RAC, Advanced Security, and Partitioning each carry additional licence costs.

Before committing to EE, organisations should evaluate whether the capability gaps can be addressed through architecture changes (such as implementing HA at the application layer rather than the database layer) or through alternative database platforms.

Option 3 — Migrate to an Alternative Database Platform

The SE1 end-of-life represents a natural migration decision point. Organisations that are not deeply committed to Oracle-specific features (PL/SQL, Oracle-specific data types, Oracle tools) should evaluate PostgreSQL, MySQL Enterprise, Microsoft SQL Server, or cloud-native database services as migration targets.

PostgreSQL in particular has matured significantly and handles many workloads that previously required Oracle SE1. The migration effort varies by workload, but for organisations running standard OLTP applications with limited Oracle-specific code, the long-term cost reduction compared to SE2 or EE can be substantial.

SE1 Compliance Risks in 2026

Running Oracle SE1 in 2026 creates several distinct compliance risks that organisations should quantify and address.

Sustaining Support Limitations

Sustaining Support does not provide new security patches. If your SE1 database holds regulated data (financial records, personal data under GDPR, healthcare records under HIPAA), running unpatched database software may breach regulatory obligations independent of Oracle licence compliance.

Virtualisation Compliance

If SE1 is running in a virtualised environment — VMware, Hyper-V, or a cloud environment — Oracle's virtualisation licensing rules apply. Oracle's position is that unless hard partitioning is in use (Oracle VM with hard partitions, Solaris Zones, IBM LPAR with capped partitions), the licence must cover all physical servers in the VMware cluster, not just the servers the database is running on. This rule applies equally to SE1 and SE2 and can dramatically increase actual licence liability.

Audit Exposure

SE1 installations are typically older, on legacy infrastructure, and less well-documented than newer deployments. Oracle audit teams target installations where asset management is weak. Before Oracle initiates a compliance review, SE1 users should document their exact SE1 licence entitlements, the server configurations in use, and any virtualisation that may affect the licence count.