Oracle Support Reductions: The All-or-Nothing Rule

Software maintenance and support fees make up a massive portion of any IT budget. For organizations running Oracle Databases, the annual 22% support fee is a recurring, inflation-adjusted cost.

Naturally, when database workloads are retired or migrated to the cloud, IT procurement teams seek to reduce support costs by canceling support for the decommissioned licenses.

However, many are hit with a rude awakening: Oracle’s "Matching Service Levels" policy (commonly known as the "All-or-Nothing" rule).

Here is how this contractual trap works and how to protect your database budget.

🛑 The Matching Service Levels Policy

Oracle’s licensing agreement states that all licenses for a specific software product line within an organization must be supported at the same level—or not supported at all.

This means you cannot selectively cancel support for retired licenses if they are grouped on the same support contract.

The Pricing Recalculation Trap

If you have a support contract covering 10 Oracle Database Enterprise Edition licenses and you attempt to cancel support for 5 retired databases, Oracle will not simply cut your support bill in half.

Instead, they will trigger a pricing recalculation:

1. They will cancel the original contract.

2. They will write a new contract for the remaining 5 active licenses.

3. However, they will strip away any historical discounts and recalculate the support fees based on the current list price of the software.

Often, the recalculated support fee for the 5 active licenses is equal to or greater than the original support fee you paid for all 10 databases combined. You end up with half the licenses for the same price.

🛡️ How to Plan Around the Support Trap

1. Separate Contracts During Procurement

When purchasing new Oracle licenses, never bundle all licenses onto a single contract. Instruct your procurement team to split the order into multiple, smaller ordering documents. This allows you to cancel support for an entire contract (e.g. for a specific project) without triggering a recalculation of your other active contracts.

2. Match Support Portfolios to Migration Timelines

Before executing a database retirement or cloud migration project, compile a baseline of which database instances are linked to which specific CSI (Customer Support Identifier) contract numbers.

3. Negotiate a ULA "Termination" Support Lock

If you are currently under an Unlimited License Agreement (ULA), negotiate a capped, multi-year support price book before the ULA expires. Ensure your side letters permit support reductions at certification without recalculation penalties.

🚀 How Licencify Protects Your Budget

Licencify’s SaaS dashboard lets you map your active Oracle Database deployments directly to your contract CSIs. By providing clear visibility into which databases are actively running and which are retired, Licencify helps IT procurement teams identify which support contracts can be cleanly terminated, preventing accidental support fee recalculation penalties.

Are you looking to optimize your Oracle support costs? Connect with our database licensing architects to audit your support contracts today.