Oracle Support Costs: Why You're Overpaying and What to Do About It

The 22 Percent Oracle Support Rate and Why It's Not Fixed

Oracle's publicly stated support rate is 22 percent of your licence list price. This figure appears everywhere in Oracle communications, in renewal estimates, and in licensing guides. Most organisations take it as a fixed, non-negotiable number. It is neither. The 22 percent rate is Oracle's opening position, not a fixed price. The rate is negotiable, and most enterprises fail to negotiate it because they do not realise negotiation is possible.

The 22 percent rate became industry standard over time, not because it represents the cost of support delivery or any rational pricing model. Oracle established it as the rate because enterprise customers accepted it without challenge. Once sufficient numbers of organisations agreed to 22 percent, it became the basis for industry expectations. This is classic anchoring. Once an anchor is set, negotiating away from it is difficult but not impossible.

The first step to reducing your support costs is to acknowledge that the 22 percent rate is a starting point for negotiation, not a predetermined outcome. Armed with this knowledge, you can apply leverage at renewal time to move the rate downward, just as you would when negotiating Oracle Cloud ERP pricing or other Oracle product costs. Most organisations achieve 5 to 15 percent reductions below the 22 percent standard when they negotiate properly. Some organisations have achieved reductions as high as 40 percent by combining support rate negotiation with third-party support alternatives and base rationalisation. For organisations considering a more fundamental review of their Oracle footprint, our analysis of when the business case for replacing Oracle finally stacks up provides a financial framework for evaluating the full replacement option.

Why the Oracle CSI Model Traps You Into Higher Costs

Oracle's Customer Support Identifier (CSI) system is designed to lock you into escalating support costs over time. The CSI model works by calculating your annual support costs based on your current licence position. When you add new licences during the year, your support cost obligation adjusts automatically. When you renew, the support base resets to your maximum licence consumption during the contract year, even if that consumption was temporary or non-representative.

This model creates a support cost trap. If you licence additional products for a one-time project, your support costs rise. When the project ends and you deactivate the licences, your support costs do not decline. They remain at the elevated level indefinitely. This happens because Oracle's renewal process takes the highest licence count during the year as your baseline going forward.

To escape this trap, you must actively manage your licence position during the contract year. If you know you will add licences temporarily for a project, document the temporary nature of this expansion before you deploy. When renewal comes, reference your documented expectations and request that your support base be calculated on your normal operating licence position, not your peak consumption. This is a negotiating point Oracle will concede if you present it properly and have documentation supporting your position.

Many organisations never have this conversation because they do not understand how the CSI system works. This is a significant negotiating opportunity. The cost of not managing this actively can be 10 to 20 percent of your annual support bill.

Premier Support versus Sustaining Support and the Real Cost Difference

Oracle offers multiple support tiers. Premier Support is Oracle's full support offering, available for the duration of the product's Extended Support lifecycle. Sustaining Support is Oracle's minimal tier, available indefinitely, but with limited benefits. Most organisations operate under the assumption that they must be on Premier Support because Sustaining Support is inadequate. This assumption costs millions across enterprise portfolios.

The practical difference between Premier Support and Sustaining Support is narrower than Oracle's marketing suggests. Sustaining Support does not include critical patches for newly discovered vulnerabilities, and it does not include new features or enhancements. For mature products where you have no plans to upgrade, Sustaining Support is often acceptable. For products where you are still actively developing or upgrading, Premier Support is necessary only if you plan to upgrade to the latest release.

The cost difference is dramatic. A database licence on Premier Support costs approximately 22 percent of licence list price per year. The same licence on Sustaining Support costs approximately 3 percent per year. For a large database environment, this difference amounts to hundreds of thousands of pounds annually. If you can move 30 to 40 percent of your Oracle estate to Sustaining Support, your total support costs decline by 15 to 20 percent with no functional consequence.

Comprehensive analysis of Premier and Sustaining Support options walks through the decision framework for each product category and shows you which products in your environment are candidates for migration to Sustaining Support without risk.

Support True-Up Traps and How to Avoid Them

Oracle's renewal process includes a "true-up" mechanism that reconciles your actual licence consumption against your support obligations. If your documented licence position has grown since the start of the current contract, your support costs adjust upward. The trap is that organisations frequently do not challenge Oracle's calculation of what you owe. Most true-ups are accepted without scrutiny, and many include errors that inflate your obligation by 5 to 10 percent.

The true-up process should trigger a comprehensive licence position review. Before you accept Oracle's true-up proposal, commission an independent audit of your installed base. Compare your actual installed base to what Oracle claims. Most organisations find discrepancies, typically in your favour. Products you retired remain in Oracle's records. Test environments counted as production. Proof of concepts recorded as permanent installations.

Once you identify these discrepancies, negotiate to exclude them from your true-up calculation. This step alone typically reduces your true-up by 8 to 12 percent. When combined with support rate negotiation and evaluation of Sustaining Support options, a well-managed true-up can reduce your annual cost increase to near zero despite Oracle's initial proposal.

Third-Party Support Alternatives: Rimini Street, Spinnaker, and Origina

Third-party support providers offer Oracle support at dramatically lower cost. Rimini Street, the largest third-party Oracle support provider, offers support at approximately 40 to 50 percent of Oracle's rates. Spinnaker Support offers similar pricing. Origina offers support for legacy Oracle products at rates as low as 10 to 15 percent of Oracle's equivalent offering.

Switching to third-party support requires careful planning. Your organisation must validate that third-party support meets your service level requirements and carries appropriate liability protection. Most third-party providers can match Oracle's support response times and escalation procedures. However, some products and configurations may not be supported by third parties.

The financial case for third-party support is strong if you can deploy it. A savings of 40 to 50 percent on your support costs has significant business impact. For a large Oracle environment supporting 500 to 800 thousand pounds in annual support costs, moving 50 percent to third-party support would save 125 to 200 thousand pounds annually. Over a five-year period, this represents savings exceeding one million pounds.

Detailed comparison of third-party support providers shows you how to evaluate options, assess Oracle's reaction, and plan a phased migration if this approach fits your environment.

Strategies to Reduce Your Support Base at Renewal

The most direct way to reduce support costs is to reduce the products and systems on support. Most organisations support products they no longer actively use, databases that have been replaced but never decommissioned, and systems retained for regulatory compliance that could be archived instead of actively supported.

At renewal time, commission a detailed review of every product and system on support. Identify systems you have moved away from but not formally retired. Identify products you have newer versions of deployed elsewhere. Identify databases running on test/development servers that do not require support. For each candidate, develop a migration, retirement, or transition plan. The cost of executing this plan is almost always far below the cost of continuing support for systems you no longer use.

A well-executed support base rationalisation typically identifies 10 to 20 percent of your current support costs as candidates for elimination. For a 750 thousand pound support bill, this represents 75 to 150 thousand pounds in annual savings. Implement this over 18 to 36 months as you retire systems and migrate workloads, and your total support cost growth during that period could be zero or even negative despite inflation and product price increases.

The Importance of Negotiating Before Renewal Date

Oracle support negotiations are most effective when you initiate them 6 to 12 months before your contract renewal date. At this point, you have time to develop alternatives, gather data on your licence position, and build a negotiating strategy. Oracle is also more flexible at this stage because they have time to accommodate your requirements.

If you wait until 30 to 60 days before renewal, your leverage evaporates. At this point, Oracle knows you are time-constrained and unlikely to complete a migration to third-party support or implement a complex rationalisation plan. Your negotiating window closes rapidly once the renewal billing date approaches.

Start your support renewal planning 12 months before expiry. Commission an independent audit of your licence position. Evaluate third-party support alternatives. Develop a list of products and systems you can rationalize. Only when you have completed this work should you engage Oracle in formal negotiations. At that point, you will have the leverage to achieve meaningful reductions.

Combining Strategies for Maximum Impact

The most effective approach to reducing support costs combines multiple strategies. First, rationalize your support base by 10 to 15 percent. Second, migrate products where possible to Sustaining Support. Third, negotiate your Premier Support rate down from 22 percent to 17 to 19 percent. Fourth, evaluate third-party support for your largest cost categories and migrate where financial case is strongest.

An organisation executing all four strategies simultaneously can typically reduce support costs by 25 to 40 percent compared to continuing at current rates with standard negotiation. This level of reduction requires more effort and planning, but the financial return justifies the investment.

Support rate negotiation tactics and true-up reduction strategies provide detailed guidance on executing each phase of this approach.