Cost Reduction & Efficiency
Forensic entitlement analysis identifies shelfware, over-licensed options, and misaligned metrics. Right-size your Oracle estate and defend your position before Oracle audits you.
Oracle's licensing model is designed to accumulate cost, not to enforce discipline about deployment. Licences you purchased five years ago for a specific purpose remain in your entitlement register even if that project was cancelled. Database options you enabled for testing remain licensed even if testing is complete. Metrics that made sense when your user base was 500 remain in place when your user base is 5,000. The 22% annual support fee you pay compounds on this growing base year after year, regardless of usage.
Most Oracle estates contain significant shelfware — licences paid for but never deployed, or deployed and then decommissioned without licence return or renegotiation. We've found instances where organisations own licences for Oracle Fusion Cloud products they never implemented, Java SE licences for developers who left the organisation, and Advanced Security options licensed but never enabled on any database. Oracle does not incentivise you to disclose this excess; Oracle incentivises you to be uncertain about what you own so you renew everything.
Database options like Partitioning, In-Memory, RAC, Diagnostics Pack, Tuning Pack, and Advanced Security are frequently over-licensed or over-deployed. These options are sold as individual add-ons but have high per-server costs. A Partitioning licence covers a single server; if you've licensed Partitioning on five servers but only use it on one, you're paying 5x for the privilege. Many organisations license these options in bulk (e.g., "all database servers") without understanding which servers actually use which features.
The Processor vs Named User Plus metric choice is rarely reviewed after initial purchase, yet it's one of the highest-leverage optimisation opportunities available. In environments where the user base is known and relatively fixed (e.g., controlled user groups, development teams, financial services operations), Named User Plus licensing can produce savings of 30–50% compared to Processor-based licensing. The opposite is true in environments with large, uncontrolled user populations or heavy batch processing. Many organisations license under the wrong metric for their actual deployment pattern.
ULAs (Unlimited Licence Agreements) are frequently under-deployed before certification. A ULA provides unlimited deployment of named products for a fixed term, but the value is only captured if you deploy significantly during the ULA period. We've found ULAs where organisations deployed 10–20% of the products covered, leaving 80–90% of the licence value unused. Worse, when the ULA expires and transitions to renewal, the baseline is your historical certified deployment, not your maximum allowed deployment. Under-deployment is a compounding financial mistake.
Support fees are rarely evaluated as an independent decision. Most organisations pay Oracle's standard 22% annual support on their entire licence value without considering whether every product truly requires ongoing Oracle support, or whether alternatives (third-party support providers, self-support, or suspension) might be more cost-effective. Support Rewards — Oracle's mechanism to credit OCI spend against support fees — is not automatically applied and requires proactive management to capture.
Complete inventory of your Oracle licence entitlements, matched against your purchase orders, order forms, and Oracle's published CSI. We identify licences you own, when they expire, and what deployment rights they carry.
Detailed analysis of which database options are licensed, deployed, and actually used. We identify over-licensed options, under-utilised features, and opportunities to consolidate options across fewer servers.
Quantitative comparison of Processor-based licensing vs Named User Plus licensing for your actual deployment pattern. We model cost under each metric and identify which is more cost-effective for your environment.
Review of your Oracle support obligation, identification of products where support can be suspended or replaced with third-party alternatives, and calculation of reinstatement fee risk.
For ULA or EA holders, negotiation of licence returns, downsize agreements, or metric conversions to align your licence position with actual deployment and reduce ongoing cost.
Where appropriate, we advise on architectural changes that reduce licensing exposure: consolidation of databases, migration from Processor to NUP-friendly applications, or deployment redesign to reduce metric-triggering configurations.
We gather all Oracle licensing documentation: purchase orders, order forms, CSI records, EA/ULA agreements, contract amendments, and prior audit/negotiation records. We create a complete map of what you own, when each licence expires, and what deployment rights are granted.
We conduct interviews with IT operations, ITAM, and application teams to map actual Oracle deployments: databases installed, options enabled, users licensed, and products deployed. We identify the gap between entitlement and deployment.
We identify licences you own but have not deployed, options you've licensed but don't use, and products licensed but not in service. We quantify the annual cost of this excess and estimate potential savings if reduced.
We model alternative licence configurations: reduced option sets, metric conversions, support rationalisation, or architectural changes. We quantify the cost of each option and present recommendations with implementation roadmaps.
We lead negotiations with Oracle to implement the optimised configuration: licence returns, metric conversions, EA/ULA restructuring, or contract amendments. We manage implementation and track realised savings.
You're accountable for IT cost reduction. A 20–40% cut in Oracle spend is immediately visible on the P&L. We quantify the savings potential and help you capture it.
You're responsible for licence compliance but may not have deep Oracle expertise. We provide the forensic analysis and recommendations to optimise your position.
You've received pressure to reduce Oracle costs. We help you identify where costs can be cut without compromising support or coverage. We help you make intelligent trade-offs.
You're managing Oracle contract renegotiation or ULA exit. We provide the technical and commercial evidence to support licence reduction or metric conversion negotiations.
A logistics company owned 15 Oracle Database Enterprise Edition instances across multiple data centres, licensed under Processor metrics (40 processors total). Our analysis identified that 8 of the 15 databases were supporting legacy systems with fewer than 50 daily active users. We modelled consolidation of these 8 databases into a smaller footprint and conversion to Named User Plus licensing for the consolidated environment. Result: Consolidated to 3 NUP-licensed instances, reduced processor cores from 40 to 8, eliminated 5 databases, eliminated 6 Diagnostics Pack and 6 Tuning Pack licences. Annual recurring savings: $3.1M. Total implementation cost: $180K. Payback: 21 days.
Comprehensive guide to Oracle Database licensing models, metrics, and optimisation strategies. Covers Named User Plus vs Processor licensing, database options, support cost reduction, and ULA strategy. Used by finance teams and ITAM professionals managing Oracle cost reduction initiatives.
Download White PaperAfter optimising your estate, negotiate better EA or ULA terms. We help you convert optimisation discoveries into contract renegotiation leverage.
Optimisation and compliance work together. Before Oracle audits you, establish a compliant, lean position that is difficult for Oracle to challenge.
Support costs compound. We help you reduce support spend on products where alternatives exist, or where support can be more cost-effectively managed.
Shelfware is licences you own but don't deploy, or options you've licensed but don't use. This includes: abandoned projects where licences were purchased but the project was cancelled or delayed; testing environments where licences were enabled and never disabled; options enabled by database administrators for investigation but never formally uninstalled; and entitlements that remain in your CSI after the systems they were purchased for were decommissioned. We quantify shelfware and estimate the annual cost.
Licence return depends on your contract. In an Enterprise Agreement (EA), you can typically return licences but only if you're reducing your baseline entitlement and Oracle agrees to a renegotiated fee. In a Perpetual Licence Agreement (PLA), you own the licences outright and cannot return them. In a ULA, returning licences is not meaningful because the ULA is unlimited; however, you can reduce your deployment at certification, which affects your future baseline. We help you understand your contractual right to return licences and negotiate the terms of return.
Named User Plus (NUP) is an Oracle licensing metric that counts specific named users who are authorised to use Oracle products. Oracle requires a minimum of 25 NUPs per CPU/server (or per instance, depending on the product). The metric is attractive in environments with a known, controlled user base (e.g., financial operations, controlled ERP deployments, development teams). NUP is typically more cost-effective than Processor licensing in environments with small user counts relative to processing power.
Processor licensing (per CPU) is more cost-effective than NUP in: (1) Environments with large, uncontrolled user populations where you cannot enforce NUP minimums; (2) Heavy batch processing environments where you're paying for computing power, not user count; (3) Cloud environments where instance sizing is variable and user counts are unpredictable; (4) Multi-tenancy environments where users span multiple instances. We model both metrics for your environment and recommend the more cost-effective option.
The most commonly over-licensed options: (1) Diagnostics Pack and Tuning Pack, which are often licensed enterprise-wide but used only by a few database administrators; (2) Partitioning, licensed per server but used on fewer servers than licensed; (3) In-Memory, licensed on all instances but used only on high-value systems; (4) Advanced Security, licensed as a baseline but not actively used; (5) RAC (Real Application Clusters), licensed for high availability but used for fewer actual deployments. We conduct option enablement audits to quantify actual usage vs licence count.
Support is 22% of Net Licence Value (NLV) per year. NLV is the total cost of your licences. If your NLV is $1M, annual support is $220K. As you add licences or convert to more expensive metrics, your NLV increases and so does your support cost. After five years with no optimisation, a growing NLV can create support costs that exceed the original licence purchase price. Support cost reduction through optimisation compounds in reverse: reducing your NLV by 30% reduces annual support costs by 30% in perpetuity.
This depends on your contract. If you're in an EA, licence reductions typically require renegotiation of the baseline. If you have a Perpetual Licence Agreement (PLA), you cannot reduce licences within the agreement term; you own them outright. However, you can decline to renew support, which reduces ongoing costs without affecting licence ownership. ULA reductions are possible through amendments before certification. We help you understand your contractual options for licence reduction outside of renewal.
We'll analyse your entitlement, identify optimisation opportunities, and quantify potential savings. At no cost.
Schedule ConsultationWe publish weekly analysis of Oracle cost optimisation strategies, shelfware identification techniques, and licensing metric comparisons. Subscribe for actionable intelligence.