Contents
Key takeawaysDoes 19c SE2 support RAC?What SEHA coversEnterprise Edition costFive options comparedCheck your own databasesMigrating without overpayingWhat we have seenWhat to do nextFAQRAC was included in the SE2 socket price through 18c and is gone from 19c. Clustering now needs Enterprise Edition plus a $23,000 per processor option, while SE2 still costs $17,500 per socket with 22 percent support.
- RAC is gone from SE2. From 19c there is no supported way to cluster Standard Edition 2 and no option to buy it back on that edition.
- Nothing was refunded. The $17,500 per socket fee and the 22 percent support line stayed the same for a smaller product.
- SEHA covers failover. Included from Release Update 19.7, it restarts one instance on a second node in minutes, with the passive node unlicensed under the ten day rule.
- The Enterprise Edition route costs far more. Two 16 core nodes with Enterprise Edition plus RAC cost past $1.1 million at list, about 32 times the SE2 licenses they replace.
- Many clusters need less. A standby or failover design met the real requirement in 30 to 40 percent of the clusters we reviewed.
- Ask for a migration. Ask for a license migration and keep SE2 support lines in place until the repricing is in writing.
Does Oracle 19c Standard Edition 2 support RAC?
No. Oracle removed Real Application Clusters from Standard Edition 2 at 19c, and there is no supported way to run clustered SE2 on 19c or any later release. No option exists to buy it back on that edition. Clustering now requires Enterprise Edition plus the RAC option at $23,000 per processor.
The upgrade path enforces the change. An SE2 RAC database must be converted to a single instance before it can be upgraded to 19c, as My Oracle Support note 2504078.1 sets out, unless you move it to Enterprise Edition first.
| 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 |
How tight was the old SE2 RAC rule?
It was tighter than most teams remember. The two socket limit applied across the entire cluster, so a supported SE2 RAC build was two single socket servers, each instance held to 8 threads. Total compute equaled one modern two socket box.
That changes what you need to replace. A 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 so in the design review is what shrinks the replacement scope.
Why did the removal hit the most compliant customers hardest?
The removal landed in 19c, the long term support release every SE2 site was being pushed toward. Oracle ended Premier Support for 18c in June 2021 with no Extended Support, while 19c runs to December 2029 on Premier and December 2032 on Extended Support.
So the customers who followed the support policy were the ones who lost the feature. The fee stayed at $17,500 per socket and support at 22 percent, for a smaller product. Oracle offered $0 in refunds, credits or support reductions.
How to Negotiate Your Oracle SaaS Renewal: The Five Moves at the Table
What is Standard Edition High Availability, and what does it replace?
SEHA is Oracle's partial replacement: a single SE2 instance that fails over between two nodes on shared storage, included at no extra license fee. It arrived with Release Update 19.7 on Linux x86-64, Solaris on SPARC and Windows, and reached AIX and HP-UX Itanium with Release Update 19.13.
It runs on Oracle Grid Infrastructure, with Clusterware and ASM or ACFS as shared storage mounted on both nodes, and it needs matched Oracle homes. When the active node fails, Clusterware restarts the database on the other one.
What SEHA does not do that RAC did
- No serving from two nodes. One instance runs at a time, so the second server adds no capacity.
- No load balancing. All connections go to the single running instance.
- No session survival. Sessions drop when the node fails and the application reconnects.
- Slower recovery. Failover takes minutes of instance restart, where RAC recovered in seconds.
For a workload clustered to survive a hardware failure, those gaps rarely matter. For one that relied on two instances serving users at once, SEHA falls short, and the decision shifts to Enterprise Edition or another platform.
How is the SEHA passive node licensed?
The passive node needs no licenses inside Oracle's ten day failover rule. It allows the database to run on an unlicensed spare node in a cluster sharing one disk array for up to ten separate days in a calendar year. Oracle sets the rule out in its Licensing Data Recovery Environments policy and applies it to SEHA.
Each server in the pair must still respect the SE2 limit of two sockets per server, although no limit applies across the cluster. Read your own copy of the rule before the architecture signs off.
Standard Edition 2 licensing brief
The SE2 rules, the 19c decision tree and SEHA design patterns in one download.
Get the white paper →How much does Enterprise Edition plus RAC cost compared with SE2?
At list, replacing a two node SE2 cluster on 16 core chips with Enterprise Edition plus RAC runs past $1.1 million, against SE2's $17,500 per socket. Across the replacements we advised, four of five negotiated outcomes landed at 3 to 6 times prior cost, and only after the design was cut back.
Worked example: one two node cluster, four designs
Say you run the classic SE2 RAC build: two servers, each with one Intel socket of 16 cores. Enterprise Edition counts cores times the 0.5 Intel core factor, so each node is 8 processors and the pair is 16. The figures use Oracle's current list prices, with support at 22 percent a year.
| Design | What you license | License at list | Annual support |
|---|---|---|---|
| SE2 RAC up to 18c | 2 sockets at $17,500 | $35,000 | $7,700 |
| SE2 with SEHA on 19c | Existing 2 socket licenses cover the primary, passive node under the ten day rule | $0 new | $7,700 |
| EE single instance, failover node under the ten day rule | 8 processors of EE at $47,500 | $380,000 | $83,600 |
| EE plus RAC on both nodes | 16 processors of EE at $47,500 plus RAC at $23,000 | $1,128,000 | $248,160 |
The last row is about 32 times the SE2 license cost for the same servers, and it is what a first quote tends to carry. The negotiated outcomes above came only after the design was reduced.
The core factor table is in our core factor analysis, and the processor rules in the database licensing reference.
Why the first quote prices the biggest design
Oracle's account team quotes what you ask about. Ask to "replace our RAC cluster" and the answer is Enterprise Edition on every core of every node with RAC on top. Every later discount is measured from that number, so cut the scope before you ask for a price. Our SE2 to Enterprise Edition cost model covers other server shapes.
Which high availability option fits an SE2 cluster on 19c?
Start from what the cluster was for. Most SE2 RAC builds bought resilience, so a failover design often meets the requirement at a fraction of the Enterprise Edition price. We price five options for every affected cluster.
- SEHA on shared storage. Included from 19.7, automatic failover in minutes, passive node unlicensed within the rule. The fit for clusters built purely for availability.
- A standby design on SE2. Data Guard needs Enterprise Edition, but storage level replication or application level standby still meets many recovery targets at SE2 prices.
- Enterprise Edition plus RAC. The full replacement, at $23,000 per processor for the option alone. Justified only where the workload needs multi node serving.
- Staying on 18c. It postpones the decision without solving it, as explained below.
- Moving the workload to another platform. Right for databases that outgrew SE2 anyway, priced against the Enterprise Edition step.
Two cheaper Enterprise Edition designs sit between SEHA and full RAC. RAC One Node lists at $10,000 per processor on top of Enterprise Edition and relocates a single instance online. An Enterprise Edition single instance with a failover node avoids the RAC option entirely. Our guide to SE2 high availability alternatives covers each option in more detail.
Why we advise against pricing Enterprise Edition plus RAC first
The usual advice is to replace like for like: the cluster had RAC, so price Enterprise Edition with RAC and fight over the discount. We disagree. The old SE2 rule capped each node at one socket and 8 threads, so those clusters were never about scale.
Write down the recovery time and recovery point the business needs, and test SEHA and standby designs against them. Take only the clusters that fail that test to Oracle for an Enterprise Edition quote.
Is staying on 18c a real option?
No. It came up in about one site in four we worked with and was rejected every time once the security patch position was priced. With Premier Support gone and no Extended Support offered, every month on 18c adds unpatched exposure.
How do you check whether your SE2 databases run RAC today?
Run a few checks on every SE2 database before the upgrade plan is written. They show which databases are clustered, how big each server is, and what your licenses cover.
- Edition. The
v$versionbanner names Standard Edition 2 or Enterprise Edition. - Clustering.
SHOW PARAMETER cluster_databasereturns TRUE on RAC, andgv$instancereturns one row per running instance. - Configuration.
srvctl config databasereports the database type and the nodes it runs on. - Sockets.
lscpuon Linux shows sockets and cores per socket for each server. - Entitlements. Ordering documents and the support renewal, matched by CSI number, show the SE2 sockets you own.
While you are there, look for Enterprise Edition features switched on by accident. Our note on hidden Enterprise features on SE2 lists the usual ones.
How do you move from SE2 to Enterprise Edition without overpaying?
Ask for a license migration, never a new purchase. A migration reprices your existing SE2 investment into the Enterprise Edition step, while a new purchase prices from zero. Finish the requirement analysis before any quote arrives.
Read Oracle's repricing rules before retiring any SE2 support line. Terminated lines reset the discount base the migration would have carried. Our guide to dropping Oracle support and reinstatement covers the cost of getting a line back.
What will the Oracle account team say, and how do you answer?
| What you will hear | What to say back |
|---|---|
| "SEHA is not RAC. If availability matters, you need Enterprise Edition." | "Our recovery target is minutes, and SEHA meets it. Show us the requirement for two instances serving at once." |
| "This is a new purchase at the standard discount." | "We are migrating licenses we already paid for. Quote it as a migration with our SE2 fees credited." |
| "You can end SE2 support now, since you are moving." | "Not until the migration order is signed and your repricing calculation is in writing." |
| "The discount holds only until quarter end." | "Our upgrade plan sets the date. We sign when the design is final." |
The history also belongs in the discount discussion. You are being asked to pay materially more to stand still, on a replacement design that was not your decision. Raise that on any Enterprise Edition step, at the renewal table.
Which contract terms should you ask for?
- Migration credit in the ordering document. It records which SE2 licenses converted and the credit applied, so a later audit or renewal cannot treat the Enterprise Edition licenses as a fresh purchase.
- Support base in writing. Support should be 22 percent of the net fee after the credit, with the old SE2 support line folded into the new one and never billed alongside it.
- Price hold on added processors. Lock the per processor price for 12 to 24 months in case more clusters fail the requirement test.
- Named configuration. List the servers, cores and failover node in scope, with the failover node confirmed under the ten day rule.
What have we seen in SE2 upgrades to 19c in 2024 and 2025?
Across roughly 30 to 45 Oracle Standard Edition customers Fredrik Filipsson reviewed in 2024 and 2025, the 19c upgrade forced a high availability redesign in more than half. In every one, the loss surfaced during upgrade planning instead of budget planning, a year too late.
- 4 of 5. Enterprise Edition plus RAC quotes landed at 3 to 6 times prior cost, affordable only after scope cuts.
- 30 to 40 percent. Clusters whose actual requirement a standby or failover design met, at a fraction of the price.
- 1 in 4. Sites where staying on 18c was floated, and rejected each time.
The sites that read the desupport list early chose their design calmly. The rest negotiated under a deadline Oracle's support policy set. In the good outcomes the requirement question did most of the work, because a cluster bought years ago for availability rarely needs multi node serving today.
A cluster built for resilience on two one socket servers is slower than the 19c single instance that replaces it.
For the edition rules in full, see our Standard Edition 2 licensing guide, and for the wider picture the Oracle licensing guide.
What to do next
- Twelve months out, read the desupport list. Do it during budget planning and put the high availability decision in that year's budget.
- Run the checks above on every SE2 database. Know which ones run RAC and how many sockets each server has.
- Define the availability requirement before any quote. Many clusters need only failover.
- Design SEHA inside the ten day failover rule. It is the included replacement, with an unlicensed passive node.
- Frame any Enterprise Edition step as a migration. Keep every SE2 support line active until the repricing is in writing.
- Raise the withdrawn feature at the renewal table. Use it on any Enterprise Edition step. The Oracle practice runs the redesign and the negotiation with you.
Want a second opinion on your Oracle position? Our Oracle licensing consultants are former Oracle insiders who now work only for buyers.
Frequently asked questions
Does Oracle Standard Edition 2 support RAC on 19c?
No. From 19c onward, including every later release, SE2 runs as a single instance only, and Oracle sells no option that adds RAC back. The clustered routes left are SEHA failover on SE2, or Enterprise Edition with RAC or RAC One Node.
What replaced RAC in Standard Edition 2?
Standard Edition High Availability, included at no extra license fee from Release Update 19.7. It needs Grid Infrastructure, shared storage and matched homes on both nodes. It never serves from both nodes, balances load or keeps sessions through a failure, so it fits workloads that must survive a hardware fault where a second serving node adds nothing.
What does replacing SE2 RAC with Enterprise Edition cost?
At list, past $1.1 million for a two node cluster on 16 core chips, since RAC is a $23,000 per processor option on top of Enterprise Edition at $47,500. SE2 cost $17,500 per socket. Negotiated results came in far lower, but only after the design was cut back from what the first quote priced.
Do most SE2 clusters actually need RAC's replacement?
Often not. Most SE2 RAC builds bought resilience, because the old rule allowed one socket and 8 threads per node. A 19c single instance can use two sockets and 16 threads, so for most affected workloads the new primary outperforms the old cluster.
Does the SEHA passive node need licenses?
Not while the database runs there for no more than ten separate days in a calendar year. Past that limit the second node needs its own SE2 licenses, so log every failover and fail back promptly after repairs.
Can you get a credit for the removed SE2 RAC feature?
No. Oracle refunded nothing, kept the fee and the 22 percent support line unchanged, and created no transition entitlement. Raise the history in the discount discussion on any Enterprise Edition step instead, where paying more to stand still is a fair point to make.
Can you upgrade an SE2 RAC database directly to 19c?
No. Oracle requires SE2 RAC databases to be converted to single instance before the 19c upgrade. Plan the conversion, the failover setup and a timed failover test as one project, well before 18c patching pressure sets the date for you.