Running Oracle without support is the option Oracle least wants customers to consider and the one most worth understanding clearly. The instinct that cancelling support somehow invalidates the software is wrong: a perpetual Oracle licence is a permanent right to use the software, and that right does not lapse when the annual support contract does. This analysis supports the Oracle support renewal pillar by examining what going unsupported actually involves, stripped of the fear that usually surrounds it.
The decision is genuinely consequential, but it is a practical risk assessment rather than a leap into the unknown. The software continues to run exactly as before. What changes is the supply of patches, updates, and vendor assistance, and the question is whether the specific estate needs that supply enough to justify a support fee that often runs to twenty two percent of the original licence cost every year, escalating with the uplift.
What does running Oracle without support mean?
Running Oracle without support means continuing to operate perpetually licensed Oracle software after declining to renew the technical support contract. The licence itself is unaffected; it was bought outright and remains valid. The support contract is a separate, annual purchase that buys access to patches, updates, new releases, and Oracle's assistance with problems. Cancelling it, the mechanics of which are set out in the support termination guide, ends that access but leaves the right to use the software intact.
This distinction between the licence and the support is the foundation of the whole decision, and it is the distinction Oracle's renewal conversations tend to blur. A customer that grasps it clearly understands that it is not choosing whether to keep its software, but whether to keep buying a service on top of software it already owns. Framed that way, the decision becomes a straightforward comparison of the support fee against the value of what the support provides for this particular system.
What you keep and what you lose
The table below sets out the position clearly, separating what survives the cancellation from what ends with it.
| Capability | With support | Without support |
|---|---|---|
| Right to use the software | Yes | Yes |
| Software keeps running | Yes | Yes |
| Security patches and bug fixes | Yes | No |
| New versions and upgrades | Yes | No |
| Oracle technical assistance | Yes | No |
| Annual support fee | Payable, with uplift | Eliminated |
The right to run the software and the software itself are unaffected. What is lost is forward looking: the stream of patches, the new releases, and the vendor's help when something breaks. For a system frozen at a stable version and well understood by its operators, that loss may be tolerable; for a system that needs regular security patching or is heading for an upgrade, it usually is not.
What are the real risks of going unsupported?
The risks are real and should not be minimised, but they are specific rather than catastrophic. The most serious is security: without patches, newly discovered vulnerabilities in the Oracle software remain unaddressed, which matters most for internet facing or sensitive systems and least for isolated, internal ones. The second is operational: without vendor assistance, the organisation must resolve incidents using its own expertise or a third party, which is feasible for mature, stable systems and risky for complex or fragile ones.
The third risk is being frozen in place: without new versions, the software cannot be upgraded through Oracle, and certifications with other products may eventually lapse. The fourth is the reinstatement penalty, discussed below, which makes returning to support expensive. None of these risks is fatal in itself, but together they define an exposure profile that must be assessed against the specific estate rather than assumed to be either trivial or ruinous, a judgement the firm advisory engagements support.
The software does not stop when support does. The real question is whether this specific system needs patches, upgrades, and vendor help enough to justify the fee, not whether you are allowed to run it.
The reinstatement penalty and the one way door
The factor that most constrains the decision is the cost of reversing it. If a customer drops support and later needs it back, Oracle charges a reinstatement fee, examined in the reinstatement guide, which typically recovers the support fees for the lapsed period plus a penalty. This converts the decision into something close to a one way door: dropping support is cheap, but returning is expensive, so the choice should be made on the assumption that it may be permanent.
This asymmetry is deliberate. It exists to deter exactly the behaviour of dropping support to save money and reinstating only when a patch or upgrade is needed. A customer considering going unsupported should therefore price the reinstatement penalty into the decision from the start, treating the support saving as durable only if the system can realistically run unsupported for the long term. Where the system is likely to need support back within a few years, the reinstatement penalty often erodes the saving entirely.
When dropping Oracle support makes sense
Dropping support makes the most sense for stable, mature systems that are not being actively developed, are well understood by their operators, are not heading for an Oracle upgrade, and sit in environments where the security exposure of unpatched software is manageable. A legacy application running a fixed Oracle version, isolated from the internet, with no upgrade on the roadmap, is a strong candidate; the support fee buys little it will ever use.
It makes the least sense for systems that are internet facing, subject to strict patching requirements, complex enough to need vendor assistance, or likely to be upgraded. For those, the support fee buys protection the system genuinely needs. The decision is therefore estate specific, and the disciplined approach segments the Oracle estate, dropping support only where the risk profile permits while retaining it where it is warranted, in line with the analysis in the premier versus sustaining support guide.
Third party support as the middle path
For many estates the choice is not binary between Oracle support and no support at all. Third party support, analysed in the third party support guide, offers a middle path: an independent provider maintains the software, often at roughly half the Oracle fee, supplying fixes and assistance without Oracle's patches or new versions. This preserves much of the operational safety net while capturing a large part of the saving, and for stable systems it is frequently the strongest option.
The middle path also softens the one way door problem, because a third party provider can support the system during the period a customer would otherwise be wholly unsupported, preserving the option to return to Oracle later on better understood terms. The interaction between third party support, reinstatement, and the renewal economics is set out across the renewal pillar and the renewal licensing white paper, which together frame the unsupported option as one point on a spectrum rather than a cliff edge.
The buyer side view
The buyer side view of running Oracle without support is that it is a legitimate, sometimes optimal choice that Oracle's renewal conversations are designed to make feel reckless. The perpetual licence survives, the software runs, and for the right estate the support fee buys little of value. The exposure is real but specific, and it is assessed system by system rather than assumed for the whole estate.
The disciplined response is to separate the licence from the support in the analysis, to assess the security and operational exposure of each system individually, to price the reinstatement penalty into the decision from the outset, and to weigh third party support as a middle path before going wholly unsupported. Read the termination guide and the third party support analysis for the connected detail, and weigh the engagement economics through the firm engagement model.
Running Oracle without support: frequently asked questions
Can I keep using Oracle software after cancelling support?
Yes. A perpetual Oracle licence survives the cancellation of support, so the software keeps running and the right to use it continues. What you lose is patches, updates, new versions, and Oracle technical support, as the termination guide explains.
What are the risks of running Oracle without support?
The main risks are unpatched security vulnerabilities, no access to bug fixes or new versions, no vendor assistance for incidents, and a costly reinstatement penalty if you later need support back, detailed in the reinstatement guide.
Is it cheaper to run Oracle without support?
It removes the entire support fee, which is a substantial saving, but the value depends on the estate. A stable, mature system may run safely unsupported for years; a system needing patches or upgrades usually should not, per the third party support analysis.
Can I get Oracle support back after dropping it?
Yes, but Oracle charges a reinstatement fee covering the lapsed period plus a penalty, which can make returning expensive. The reinstatement economics should be understood before support is dropped, not after.