Skip to content
20th April 2026

A Must Read Before Your Oracle Support Renewal

Back To Resources
An unlocked Padlock, free yourself from Oracle ULA problems

Oracle Support renewal should never be treated as a routine administrative task. For many organisations, it represents one of the largest recurring IT expenditures, often increasing annually while delivering diminishing value. 

Understanding how Oracle structures renewals, where risks lie, and what alternatives exist is essential to controlling long term costs and protecting your IT strategy.

How Oracle Support Renewals Work

Oracle renewals now generally fall into two categories, each with its own cost risks:

  • Perpetual Licences: You own the software indefinitely, but pay an optional annual fee for support (typically 22 per cent of the original cost). These fees often increase by 4 per cent annually.
  • SaaS Subscriptions: A newer model where you must renew annually. If you stop paying, you lose access to the system entirely.

In both scenarios, Oracle has introduced structural changes to the renewal process. These reduce flexibility and make automatic continuation the default, often catching organisations off guard.

Automatic Renewal and Notice Periods

Many Oracle customers are now subject to automatic renewal provisions. Instead of expiring at the end of the support term, contracts renew automatically unless written notice is provided within a defined window.

Key risks include:

  • Short opt-out periods, commonly around 30 days before renewal
  • Renewal lockdown once the notice window passes
  • Automatic application of Oracle’s current annual uplift percentage

Many organisations miss these deadlines and become committed to another full year of support at increased cost.

Compounding Oracle Price Increases

An annual 4 percent increase may appear manageable. Over ten years, however, this compounds significantly. A support contract of 500,000 per year becomes more than 740,000 annually after a decade of uninterrupted uplifts.

Because support fees are based on historic licence purchases rather than current usage or value received, organisations often pay increasing amounts for systems that are stable, lightly used, or no longer strategically important.

Matching Service Levels Confusion

Oracle’s matching service levels policy is frequently misunderstood during renewal discussions.

The policy requires that products within the same licence set on a single system are supported at the same level. It does not require that every Oracle product ever purchased must remain on Oracle support.

Some organisations are incorrectly advised that partial termination is not permitted. This is not accurate. You can reduce scope, retire environments, or move selected systems off Oracle support provided you remain compliant with licence terms.

Download Restrictions Before Renewal

Oracle has introduced limits within its Support Portal Terms of Use, including restrictions on the volume of files that may be downloaded per user per day.

If you are considering leaving Oracle support at renewal, planning ahead is critical. Patches and updates to which you are entitled should be downloaded and archived in advance, within contractual boundaries.

Negotiating an Oracle Support Renewal

Renewal does not automatically mean acceptance of list price increases.

Organisations can:

  • Review actual product usage and eliminate shelfware
  • Consolidate or retire non-strategic environments
  • Rebaseline support footprints
  • Leverage competitive alternatives during negotiation

Timing is critical. Negotiation leverage decreases significantly once you are inside an automatic renewal window.

Considering Third Party Support at Renewal

Oracle support is optional. The licence is perpetual, but the support contract can be terminated at renewal with appropriate notice.

Third party Oracle support providers such as Support Revolution typically offer:

  • Up to 50 percent reduction in annual support fees
  • Support for custom code
  • No mandatory upgrades
  • Tailored security and legislative updates
  • Longer product lifecycles

For many organisations, renewal season is the natural decision point to evaluate whether continued Oracle support aligns with business objectives.

A Structured Transition Approach

Moving away from Oracle support requires planning, but it is not complex when managed properly.

A structured transition process typically includes:

  • Formal transition planning with defined roles and timelines
  • Identification and archiving of entitled patches and versions
  • Review and migration of open support incidents
  • Establishment of system access where required
  • Go live under a new support model

Take Control of Your Renewal

Oracle Support renewal should be a strategic review, not a default payment.

Before accepting renewal terms:

  • Confirm whether automatic renewal applies
  • Validate notice deadlines
  • Assess real business value from current support
  • Quantify long-term cost escalation
  • Evaluate alternative support models

With proper preparation, renewal becomes a point of leverage rather than a vendor controlled event.