Standard Edition RAC in 19c. What actually changed.

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, the Oracle core factor explained guide, and the Oracle Practice page.

What changed for Standard Edition RAC in 19c?

The headline is simple. RAC is gone from Standard Edition 2 in 19c. Oracle confirmed the removal in its 19c upgrade documentation, and there is no supported way to run a clustered SE2 database on the release.

How did SE2 RAC work up to 18c?

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.

• Edition: Standard Edition 2, licensed per socket.
• Cluster: RAC included, no separate option fee.
• Limit: the SE2 socket cap still applied across the cluster.

What does SE2 allow from 19c onward?

From 19c, SE2 is single instance only. Oracle documents the change on its Oracle Database product pages and in the upgrade notes. If you stay on SE2, you give up clustered RAC.

What are your options if you still need RAC?

The choice comes down to whether clustering is a hard requirement or a nice to have. Each path has a clear cost and risk profile.

What does Enterprise Edition plus RAC cost?

Enterprise Edition licenses per processor with the core factor, and the RAC option is a separate per processor charge on top. For a cluster that was previously free on SE2, that is a substantial jump, often several times the prior cost.

Are there alternatives to a full RAC move?

Sometimes. If your real need is failover rather than active active scaling, a standby database may meet the requirement at lower cost. Confirm which high availability features need Enterprise before you assume RAC is the only answer.

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.

What to do next

1. Confirm whether any SE2 database in scope relies on RAC today.
2. Decide if clustering is a hard requirement or really a failover need.
3. Model Enterprise Edition plus the RAC option per processor with the core factor.
4. Compare that against a single instance SE2 design with a standby database.
5. Check support timelines so you are not stranded on 18c for the feature.
6. Fold any edition change into your wider Oracle contract, not a one off quote.
7. Document the chosen design before the upgrade so audit posture stays clean.

Frequently asked questions

Can you run RAC on Oracle Standard Edition in 19c?

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 must move to Enterprise Edition with the RAC option.

Up to which version did SE2 RAC work?

Standard Edition 2 supported RAC through 18c, within the socket limits and at no extra license cost. The removal took effect in 19c, which is the long term support release most enterprises are upgrading to.

How is Standard Edition 2 licensed in 19c?

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.

How much more does Enterprise Edition plus RAC cost?

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 move is often several times the prior license cost.

Is a standby database an alternative to RAC?

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.

Should we stay on 18c to keep SE2 RAC?

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.