Oracle SE2 RAC in 19c
Standard Edition RAC in 19c. What actually changed.
A buyer side guide to Oracle Standard Edition RAC and the 19c change. Why SE2 RAC is gone, what SE2 still allows, and the licensing path if you still need clustering.
A buyer side guide to Oracle Standard Edition RAC and the 19c change. Why SE2 RAC is gone, what SE2 still allows, and the licensing path if you still need clustering.
Oracle Real Application Clusters on Standard Edition is no longer supported from 19c onward. Oracle removed RAC from Standard Edition 2 in that release, so a clustering design that was free under SE2 now forces a different licensing path.
This guide is for Oracle DBAs and procurement teams planning a 19c upgrade in 2026. Read it with the Oracle Database license cost guide and the Oracle core factor guide.
RAC is gone from Standard Edition 2 in 19c. There is no supported way to run a clustered SE2 database on the release. Oracle states the removal in its 19c upgrade documentation.
Through 18c, Standard Edition 2 included RAC at no extra license cost, within the socket limits. That made a small, highly available cluster affordable on SE2.
From 19c, SE2 is single instance only. The metric is unchanged, but the clustering capability is withdrawn. Oracle keeps the edition rules on its Oracle Database product pages.
The choice turns on whether clustering is a hard requirement or a nice to have. Each path has a clear cost and risk profile.
SE2 RAC removal in 19c, the options compared
| Path | Clustering | Licensing impact |
|---|---|---|
| Stay on SE2 19c | Single instance only | No change, per socket |
| Move to Enterprise plus RAC | Full RAC clustering | Per processor, large increase |
| Standby with Data Guard | Failover, not active active | Enterprise needed for advanced standby |
| Stay on 18c | SE2 RAC retained | Out of premier support |
Often yes. If the real need is failover, not active active scaling, a standby database can meet it. Confirm which high availability features require Enterprise before you assume RAC is the only answer.
White Paper ยท Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
Enterprise Edition licenses per processor with the core factor, and the RAC option is a separate per processor charge on top. The list mechanics sit in the Oracle Technology Price List.
Two charges stack. The Enterprise license replaces a per socket SE2 fee, and the RAC option adds a second per processor line. The Oracle core factor table then sets how many processor licenses each core counts as.
The standard reseller pitch is that losing SE2 RAC means you simply buy Enterprise Edition and the RAC option, and move on. We disagree. In roughly half of the SE2 estates we reviewed, the workload never needed active active scaling at all, so the cluster was solving a failover problem that a standby pair handles for a fraction of the cost. Paying for Enterprise plus RAC to replace a feature you were using as insurance is the most expensive way out. The buyer side move is to separate the real requirement, failover or scaling, before any quote is modeled.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Losing SE2 RAC in 19c is not a feature footnote. It is a high availability redesign with a real license bill attached, so plan it as an architecture decision, not an upgrade detail.
Treat the edition change as a design step, not a quote. Decide the target architecture first, then price it.
No. Oracle removed RAC from Standard Edition 2 starting with 19c, so SE2 runs single instance only on that release. To keep clustered RAC you move to Enterprise Edition with the RAC option.
Standard Edition 2 supported RAC through 18c, within the socket limits and at no extra license cost. The removal took effect in 19c, the long term support release most enterprises now run.
SE2 still licenses per socket, capped at two sockets per server. The metric did not change in 19c. What changed is that the clustered RAC capability is no longer available on the edition.
Enterprise Edition licenses per processor with the core factor, and RAC is a separate per processor option on top. For a cluster that was free under SE2, the step is often three to six times the prior cost.
It can be. If your requirement is failover rather than active active scaling, a standby with Data Guard may meet it. Confirm which standby features need Enterprise Edition, since some advanced options are not free.
Rarely a good idea. Staying on 18c keeps SE2 RAC but moves you out of premier support, which raises security and compliance risk. Plan a supported design rather than freezing on an old release.
No. SE2 is licensed per socket and the core factor table does not apply to it. The core factor only enters the picture once you move a workload to Enterprise Edition licensed per processor.
No tool converts the licensing for you. The upgrade can move the data, but the clustered design must be rebuilt as single instance SE2, a standby pair, or Enterprise Edition plus RAC before you go live.
Oracle ULA exit moves, Java audit defense posture, certification framework, and the buyer side moves across the Oracle Database, options, middleware, and applications estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Losing SE2 RAC in 19c is not a feature footnote. It is a high availability redesign with a real license bill attached, so plan it as an architecture decision, not an upgrade detail.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One short note on Oracle licensing moves, price list mechanics, audit posture, and the buyer side levers we run in client engagements. No noise.
