Oracle ULA and Third-Party Support: Can You Exit After Certification?

How Support Changes After ULA Certification

During the ULA term, Oracle support is tied to the ULA contract. The ULA grants deployment rights in exchange for annual support payments — support and the unlimited deployment right are bundled. Exiting Oracle support during the ULA term would put the entire deployment right at risk, because the ULA contract typically requires that support remains current as a condition of maintaining ULA compliance.

After certification, everything changes. The ULA converts to perpetual licenses — the deployment right is no longer conditional on support currency. Your perpetual licenses are yours whether you pay Oracle support or not. Oracle cannot revoke perpetual licenses for failure to pay support. The support contract is a separate annual obligation, not a condition of license ownership.

This is the single most important post-certification insight for enterprises carrying large Oracle support bills: certification is the moment at which the commercial relationship fundamentally shifts in the customer's favor. Oracle loses its primary leverage — the threat of non-compliance — because the perpetual licenses are now clean and certified. The question of whether to continue paying 22% annually to Oracle is now genuinely a commercial choice, not a compliance requirement.

What Oracle's 22% Annual Support Actually Provides

Oracle's Premier Support (the standard 22% support tier) provides: access to My Oracle Support (MOS) knowledge base and bug database, new security patches and critical patch updates (CPUs), software version updates (major and minor releases), and technical support from Oracle engineers for supported issues. Premier Support is available for five years after a product's general availability date, after which it transitions to Extended Support (additional fee) or Sustaining Support (limited service).

The reality for most large Oracle Database installations: the actual support consumption represents a small fraction of the annual support cost. Enterprise Oracle Database environments running stable versions require few patches per year, rarely submit Oracle Service Requests, and almost never use Oracle's technical support for architectural guidance. The 22% annual payment funds a service level that is significantly misaligned with actual consumption for stable production environments.

There are legitimate reasons to maintain Oracle support for certain scenarios: active development environments requiring current versions, environments in Oracle's Sustaining Support tier where patches are rare, and Oracle Application environments (EBS, PeopleSoft) where Oracle support is more actively consumed. The key is distinguishing which Oracle products genuinely require Oracle's active support and which do not.

Third-Party Support: The Commercial Case

Third-party Oracle support providers — principally Rimini Street and Spinnaker Support — provide Oracle Database support services at rates of 50% or less of Oracle's annual support cost. Their service model focuses on: providing equivalent support for existing Oracle software versions without version upgrades, delivering tax and legal change updates for Oracle applications, providing custom bug fixes and workarounds for issues not addressed by Oracle, and offering engineering support that matches or exceeds Oracle's SLAs for most support categories.

The financial case is compelling. For a large enterprise with $10M per year in Oracle Database support costs, moving to third-party support saves $5M–$8M annually — every year. Over a 5-year period, that is $25M–$40M in saved support costs. For enterprises approaching a platform migration or planning to reduce their Oracle footprint, third-party support bridges the gap between current consumption and the migration endpoint without paying Oracle for update access that will never be consumed. Our insurance company third-party support case study documents $2.8M per year in annual savings from exactly this transition.

Oracle's Objections to Third-Party Support

Oracle's sales and support teams will aggressively push back against any customer considering third-party support. The objections Oracle raises are not neutral — they are Oracle's commercial interests dressed as technical concerns. Understanding each objection and the evidence-based response is essential for any enterprise evaluating the transition.

"You will lose access to security patches." This is Oracle's most effective argument and has partial merit. Moving to third-party support means you will not automatically receive Oracle's quarterly Critical Patch Updates (CPUs). However, most CPUs address vulnerabilities in Oracle products you are not using or in configurations you do not have. Third-party support providers backport critical security fixes to your current version. Your security posture needs independent assessment — it is not automatically worse on third-party support for well-maintained, network-segmented Oracle environments.

"Third-party support is not legal." This has been litigated extensively. In the United States and European Union, enterprise customers have the legal right to use third-party support for their own perpetual software licenses. Oracle's litigation against Rimini Street primarily concerned Rimini's internal processes for handling Oracle software, not customers' right to use third-party support. Customers that have transitioned to third-party support face no legal risk from Oracle related to their license validity.

"You will not be able to re-join Oracle support later." This is partially true but highly exaggerated. Oracle's standard policy is that customers who lapse Oracle support and wish to re-join must pay back-due support from the lapse date plus a reinstatement penalty. This is a real cost that must be modelled in the decision — but for enterprises committed to a migration roadmap that eliminates Oracle, it is irrelevant. For enterprises that may want to return to Oracle support, the reinstatement cost must be factored into the total cost of ownership calculation.

"You will not get support for database version upgrades." Accurate. Third-party support does not provide new version access. If your roadmap requires Oracle Database version upgrades (from 19c to 23ai, for example), you need Oracle support for those upgrades. Third-party support is appropriate for organizations running stable versions with no planned Oracle version upgrades.

Your Contractual Rights to Exit Oracle Support

Oracle's standard support contract is an annual obligation. It is not a perpetual obligation tied to the software license. You have the right to terminate Oracle support with notice (typically stated as 30 days or end-of-contract-year notice). Oracle cannot prevent a customer from exiting support — the software license is separate from the support contract and terminating support does not affect the license validity.

The ULA certification process produces a certification letter and an amended Oracle license agreement that reflects the certified perpetual license quantities. This document confirms your perpetual license entitlement. The support contract is a separate annual document. Reviewing the exact language of your support contract with Oracle-specialist legal counsel before giving notice is strongly recommended — some support contracts contain clauses that create complications, such as cross-contract dependencies or bundled support for multiple products that must be cancelled together.

Oracle has, in some cases, attempted to include contract language during ULA negotiations that restricts the customer's ability to exit Oracle support for a defined period post-certification. These clauses are negotiable — and should be challenged during the ULA negotiation phase, not after certification has locked in the contract terms. Our ULA negotiation guide covers this as one of the 15 contract terms to push back on.

Planning the Support Transition

A successful transition from Oracle support to third-party support requires 3–6 months of preparation to avoid service disruption and to manage Oracle's account team relationship through the transition. The key elements of the transition plan are: Oracle product inventory validation, third-party support provider selection and contractual negotiation, internal knowledge transfer, and Oracle notification management.

The Oracle notification process should be handled carefully. Oracle account teams use the support cancellation conversation as an opportunity to apply retention pressure — including threats about reinstatement costs, audit risk, and security vulnerability. These conversations should be managed by your commercial negotiation team with external advisory support, not left to IT staff who may not be equipped to handle Oracle's objection playbook. Our support reduction service manages the Oracle notification process as part of every engagement.

The timing of the transition matters. Moving to third-party support at Oracle contract renewal (rather than mid-term) avoids prepaid support cost write-offs and gives maximum notice period. Planning the transition 12 months before Oracle support renewal gives time to complete provider selection, negotiate third-party contracts, and run the two providers in parallel for a brief period before cutting over.

Hybrid Support: What to Keep With Oracle

For enterprises with complex Oracle estates spanning Database, Applications, and Middleware, a full exit from Oracle support may not be optimal. The hybrid approach — third-party support for stable Oracle Database environments, Oracle support retained for Oracle Applications (EBS, PeopleSoft) where support is more actively consumed — often delivers the best financial outcome with lowest transition risk.

Oracle Applications support, particularly for Fusion Cloud (Oracle SaaS), is inherently tied to Oracle as the provider because Oracle controls the upgrade schedule and the cloud infrastructure. Fusion Cloud support cannot be moved to a third party. Oracle EBS and PeopleSoft on-premise support can technically move to a third party, but the cost-benefit calculation is different from Oracle Database — applications generate more actual support tickets and the tax and legal update dependency creates more genuine Oracle support consumption.

Oracle Middleware (WebLogic, SOA Suite) is another category where the hybrid approach applies: WebLogic support can move to third parties but requires careful assessment of whether the WebLogic version is actively being used and whether version stability is sufficient. Our license optimization service builds the full hybrid support model for complex Oracle estates, identifying exactly which products benefit from third-party support and which should stay with Oracle.