Oracle support renewal — cap the uplift, defend the perpetual.

22% × 1.08^n — the compounding.

Oracle Premier Support is priced at 22% of the licence list price per year. The "list price" reference is important: support is calculated against list, not against the discounted price the customer paid. A $10M licence purchase taken at 50% discount still attracts $2.2M per year in support against the $10M list reference. Combined with the standard 8% annual uplift clause, the support stream compounds rapidly. Year 1: $2.2M. Year 5: $3.0M. Year 10: $4.4M. Year 15: $6.5M. Cumulative ten-year support: $31.9M against an original $5M net licence purchase. Bringing that compounding stream back down is the core of any Oracle license cost reduction exercise.

Oracle's commercial strategy depends on this annuity. Support is the largest single line on Oracle's revenue — historically more than 50% of total revenue — and customer support renewal compliance is one of the most carefully managed metrics inside Oracle. From the customer side, the renewal is a high-leverage moment because Oracle's renewal target is "no termination, no reduction". Customers willing to credibly challenge those defaults regain pricing power.

Matched-set rules

Oracle's "Matching Service Levels" policy requires customers to maintain support at the same level across a contractual set. The intent is to prevent customers from supporting half of their entitlements and terminating support on the other half. The practical effect is that customers wishing to drop support on under-used licences typically need to address the entire contract, not the specific licences. This rule is contestable in negotiation but is the default position Oracle will assert.

Where pressure actually moves the number.

Several levers reduce or constrain Oracle support cost. Some require contractual change; others require operational change. In our practice, the levers that move the number:

1. Drop unused licences. Customers carrying licences they have decommissioned can terminate support on those entitlements (subject to matched-service rules). This is the most common and lowest-risk reduction lever.
2. Cap or remove the annual uplift. The 8% uplift is contractual but often negotiable at renewal. Customers who commit to a multi-year support agreement can typically negotiate a lower or capped uplift.
3. Restructure into a ULA. Moving to an Unlimited Licence Agreement converts the support stream into a defined commitment for a defined term. ULA support is calculated differently and often comes with negotiated uplift caps.
4. Migrate to OCI. Oracle's Universal Credit programmes often include support credit offsetting on-prem support payments. Customers willing to commit to OCI can restructure existing support obligations.
5. Bundle into a unified support agreement. Customers with mixed Oracle products (Database, Applications, Middleware) can sometimes negotiate a bundled support agreement at a percentage point lower than the sum of individual streams.
6. Third-party support. Moving from Oracle Premier Support to Rimini Street or Spinnaker can reduce support cost by 50%, with the trade-off of losing access to new versions, security patches and Oracle support cases.

Rimini, Spinnaker, and the trade-offs.

Third-party support (TPS) for Oracle products is offered most prominently by Rimini Street, Spinnaker Support, and a few specialist regional providers. The commercial proposition is straightforward: 50% cost reduction against Oracle Premier Support, multi-year price predictability, and broader functional support (tax updates, regulatory updates, custom code support) than Oracle provides natively. The trade-offs are equally clear: no access to new product versions, no access to Oracle's MOS support portal, no patches from Oracle, and the loss of "Matching Service Levels" entitlement.

TPS makes sense for stable, mature workloads where the version in use is not changing — particularly EBS deployments, JD Edwards, Siebel, Hyperion, and stable database workloads on supported version branches. It does not make sense for products under active development, products subject to mandatory regulatory updates that Oracle controls (some financial reporting modules), or environments scheduled for migration to OCI within the TPS contract term.

The legal landscape

Oracle's litigation against Rimini Street over Oracle's intellectual property has reshaped the TPS landscape since 2010. The most recent court rulings have clarified what TPS providers can and cannot do — Rimini Street remains operational under defined constraints. For customers considering TPS, the legal landscape is sufficiently stable that the commercial proposition is real, but contractual diligence on the specific TPS provider's offering is essential.

Why the call is not where the deal happens.

Oracle's renewal process begins 90 days before the renewal anniversary with a renewal letter listing the entitlements, the support fee for the upcoming year, and the renewal date. Customers who treat this letter as a routine invoice typically renew at full headline price. Customers who treat it as the opening of a negotiation typically achieve material concessions. The 90-day window has structure:

• Day 0-30: Review entitlements against actual usage. Identify unused, redundant, or decommissioned licences. Build the position on what should be renewed and what should be dropped.
• Day 30-60: Initial Oracle conversation. Indicate the position (drop or reduce on specific entitlements, capped uplift, multi-year structure). Test Oracle's initial response.
• Day 60-80: Counter-proposal exchange. Oracle's first counter is typically a "loyalty discount" of 1-3%. The real concession is on uplift, term, and dropped licences.
• Day 80-90: Final commercial structure. Customer commits to the agreed structure; renewal documents are issued.