SE2 RAC at 19c, paying materially more to stand still
Oracle removed Real Application Clusters from Standard Edition 2 at 19c: a clustering capability included in the socket price through 18c now requires Enterprise Edition plus a $23,000 per processor option, and the SE2 support bill did not move a cent when the feature left. The same $17,500 per socket and the same 22 percent support line now buy a smaller product, and the buyers most compliant about staying supported were the ones who lost the feature.
Prepared by Redress Compliance · August 8, 2026 · Oracle advisory. Based on 30 to 45 Oracle Standard Edition estate reviews run 2024 to 2025.
Executive summary
The wall is functional, not contractual, and it was discovered too late everywhere.
There is no supported way to run clustered SE2 on 19c or any later release and no option to restore it on that edition: the change forced a high availability redesign in more than half our estates, and the loss was discovered during upgrade planning.
Not before it, because nobody had read the desupport list at budget time.
The sequencing is the sting: the removal landed in 19c, the long term support release every SE2 site was being pushed toward, so compliance with support policy is what triggered the loss.
The Enterprise Edition replacement prices at 3 to 6 times prior cost, after scope cuts.
At list, replacing a two node SE2 cluster with Enterprise Edition plus RAC on 16 core chips runs past $1.1 million, against SE2's $17,500 per socket, and negotiated outcomes landed at three to six times prior cost in four of five cases, only after the design was cut back.
The counter question is what the cluster was actually for: a standby or failover design met the real requirement in 30 to 40 percent of clusters at a fraction of the price, because most SE2 RAC builds bought resilience, not scale.
SEHA is the partial replacement, and it quietly raises the ceiling.
Standard Edition High Availability, included from Release Update 19.7, fails a single instance over between two nodes on shared storage: it does not serve from both nodes, load balance, or hold sessions through a failure, and recovery is minutes of instance restart, not RAC's seconds.
The unpriced upside: single instance SE2 on 19c occupies a full two socket server with 16 threads, where the old cluster rule gave each node one socket and 8 threads, so workloads clustered for availability rather than throughput run faster on the new primary.
And the passive node needs no licenses inside the ten day failover rule.
The grievance converts to leverage at the renewal table, nowhere else.
Oracle offers no credit for the withdrawn capability and asking wastes a meeting, but the history is a fair argument with the account team: we are being asked to pay materially more to stand still, and the replacement design was not our decision.
Deployed to shape the discount on any Enterprise Edition step.
Ask for a license migration rather than a new purchase, read the repricing rules before retiring any SE2 support line, and price staying on 18c honestly, floated in one estate in four and rejected every time once the security patch position was priced.
SE2 clustering, before and after 19c
| Dimension | SE2 up to 18c | SE2 from 19c |
|---|---|---|
| Clustering | RAC included in the socket price | Single instance only |
| Hardware rule | Two sockets total across the whole cluster | Two socket capacity per server |
| Thread ceiling | 8 CPU threads per instance under RAC | 16 CPU threads for the database |
| High availability | Node failure survived by the surviving instance | SEHA from 19.7, or nothing |
| License fee and support | $17,500 per socket, 22 percent | $17,500 per socket, 22 percent, unchanged |
The old rule was tighter than people remember, which changes what needs replacing.
The two socket limit applied across the entire cluster, so a supported SE2 RAC build was two single socket servers with each instance held to 8 threads: resilience, not scale, with total compute equal to one modern two socket box.
The 19c single instance on a full two socket server with 16 threads is faster on the primary than the old cluster ever was, and saying that out loud in the design review is what shrinks the replacement scope.
The five options, priced honestly
- SEHA on shared storage: included from 19.7, automatic failover in minutes, the passive node unlicensed inside the ten day rule, and the fit for the 30 to 40 percent clustered purely for availability.
- A standby design: Data Guard style redundancy needs Enterprise Edition, but simpler storage level or application level standby patterns meet many requirements at SE2 prices.
- Enterprise Edition plus RAC: the full replacement at $23,000 per processor for the option alone, the 3 to 6 times outcome, justified only where genuine multi node serving is required.
- Staying on 18c: floated in one estate in four, rejected every time once the security patch position was priced, and not a plan.
- Re platforming the workload: the honest fifth option for databases whose requirements outgrew SE2 anyway, priced against the EE step rather than assumed away.
The Standard Edition 2 licensing brief
The SE2 rules, the 19c decision tree, the SEHA design patterns, and the EE step negotiation worked on a representative estate.
Get the white paper →Migrating without overpaying
The commercial mechanics decide the outcome as much as the design: ask for a license migration rather than a new purchase, because migration paths reprice existing SE2 investment into the EE step while a new purchase prices from zero.
Read Oracle's repricing rules before retiring any SE2 support line, since terminated lines reset the discount base the migration would have carried.
And run the requirement analysis before any quote arrives, because four of five EE quotes only became affordable after scope was cut, which means the first quote always priced the maximal design.
The edition arithmetic underneath, thread ceilings, socket rules, and the core factor table on the EE side, runs through the database licensing reference and the core factor analysis, and the wider estate picture in the Oracle licensing guide.
- 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 SE2 estates, 2024 to 2025
Across roughly 30 to 45 Oracle Standard Edition estates Fredrik Filipsson reviewed in 2024 and 2025, the 19c upgrade forced a high availability redesign in more than half:
Enterprise Edition plus RAC quotes against prior cost, affordable only after scope cuts.
Clusters whose actual requirement a standby or failover design met at a fraction of the price.
The discovery pattern is the fixable failure: the loss surfaced during upgrade planning rather than budget planning in every estate, which means the desupport list was read a year too late.
And the estates that read it early chose their design calmly while the rest negotiated under a deadline Oracle's support policy set.
The requirement question does the heavy lifting in every good outcome, because a cluster bought years ago for availability does not need multi node serving today, and the 19c single instance ceiling, two sockets and 16 threads against the old one socket and 8 per node.
Means the smaller design is also the faster one for most of the workloads involved.
Your first five moves
- Read the desupport list at budget time, not upgrade time, the year of warning every estate missed.
- Define the actual availability requirement before any quote, because 30 to 40 percent of clusters need failover, not RAC.
- Design SEHA inside the ten day failover rule, the included replacement with an unlicensed passive node.
- Ask for a license migration, never a new purchase, and read the repricing rules before retiring support lines.
- Use the withdrawn feature as discount leverage on any EE step, at the renewal table. The Oracle practice runs the redesign with you.
Frequently asked questions
Does Oracle Standard Edition 2 support RAC on 19c?
No: Real Application Clusters is not available with SE2 from Oracle Database 19c onward, with no supported way to run clustered SE2 on 19c or any later release and no purchasable option to restore it on that edition.
It is a functional wall, not a compliance gray area, and the removal landed in the long term support release every SE2 site was being pushed toward.
What replaced RAC in Standard Edition 2?
Standard Edition High Availability, included at no extra license fee from Release Update 19.7: automatic failover of a single instance between two nodes on shared storage, requiring Grid Infrastructure and matched homes.
It does not serve from both nodes, load balance, or hold sessions through failure, and recovery is minutes of instance restart rather than RAC's seconds, which is why it fits availability requirements, not scale ones.
What does replacing SE2 RAC with Enterprise Edition cost?
At list, past $1.1 million for a two node cluster on 16 core chips, with RAC alone a $23,000 per processor option on top of Enterprise Edition, against SE2's $17,500 per socket.
Negotiated outcomes landed at three to six times prior cost in four of five cases, and only after the design was cut back from what the first quote priced.
Do most SE2 clusters actually need RAC's replacement?
Often not: a standby or failover design met the actual requirement in 30 to 40 percent of the clusters we reviewed, at a fraction of the EE price, because most SE2 RAC builds bought resilience rather than scale.
The old rule capped each node at one socket and 8 threads, so the 19c single instance ceiling of two sockets and 16 threads is faster on the primary for most affected workloads.
Does the SEHA passive node need licenses?
No, provided the deployment stays inside Oracle's ten day failover rule in the Database Licensing Information manual, which permits the unlicensed passive node for failover use within the rule's limits.
The rule is the whole licensing story of the SEHA design, and reading your own copy of it before the architecture signs off is what keeps the included replacement actually free.
Can you get a credit for the removed SE2 RAC feature?
No: nothing was refunded, the license fee and 22 percent support line did not move, and no transition entitlement exists, so asking support for a credit wastes a meeting.
The history converts to leverage at the renewal table instead: being asked to pay materially more to stand still, on a replacement design that was not your decision, is a fair argument for shaping the discount on any Enterprise Edition step.
