We have answered Oracle licensing questions for over a decade — across 200+ engagements, every major industry, and every Oracle product family. The same 50 questions come up in nearly every engagement. They come up because Oracle's licensing model is deliberately complex, because the documentation is written to protect Oracle's position rather than clarify yours, and because the commercial consequences of getting an answer wrong are measured in six and seven figures.
This FAQ is organised differently from anything else you will find. Instead of alphabetical order or product categories, the questions are sequenced in the order you will encounter them — from the moment you inherit an Oracle estate, through your first audit, your first renewal, your first Oracle BYOL licensing migration discussion, and finally to the strategic decisions that determine whether Oracle costs you $3M or $1M per year.
"Every question below has two answers: the one Oracle will give you (technically correct, commercially advantageous to Oracle) and the one your organisation needs (the commercial reality that determines what you actually pay). This FAQ provides the second answer."
Explore More Licensing Hubs
Ready to Take Control of Your Software Licensing?
Book a free consultation with our licensing specialists. No obligations, no vendor ties — just independent advice tailored to your situation.
Book Your Free Consultation →
The Fundamentals: Questions 1–10
These are the questions you ask when you first encounter Oracle licensing — or when a new CIO, procurement lead, or SAM manager inherits an Oracle estate and needs to understand the landscape quickly.
1What is an Oracle licence, and what do I actually own?+
An Oracle licence is a perpetual right to run a specific Oracle programme (Database, WebLogic, E-Business Suite, etc.) under the terms defined in your Oracle License and Services Agreement (OLSA) and the associated Ordering Documents. "Perpetual" means you own the right to use the software forever — it does not expire. However, the licence alone does not include updates, patches, or technical support. Those require a separate, annual support contract.
Commercial reality: Your licence is perpetual but your support obligation feels permanent — Oracle charges 22% of the Net Licence Fee annually, and the
reinstatement penalty (150% of back-support) makes dropping and resuming support prohibitively expensive. You own the licence; Oracle owns the leverage.
2What is the OLSA, and why does it matter?+
The Oracle License and Services Agreement is the master framework governing your entire Oracle relationship. It defines audit rights, termination provisions, acceptable use, and liability. Most organisations signed their OLSA 10–20 years ago and have never
renegotiated it. Every commercial interaction with Oracle is governed by this document.
Commercial reality: Your OLSA is negotiable — including the audit clause (Section 10), indemnification terms, and termination provisions. Organisations that renegotiate their OLSA before a major renewal or audit gain structural advantages that compound over every future interaction. See the
Contract Terms Glossary for a full breakdown.
3What is an Ordering Document, and how many should I have?+
An Ordering Document (OD) is the specific purchase record for each Oracle transaction — it defines the products licensed, the metric, the quantity, the discount, and the resulting Net Licence Fee. Your total Oracle entitlement is the sum of all Ordering Documents accumulated over the life of your Oracle relationship. Most enterprise customers have 10–40 ODs spanning 15–20 years.
Commercial reality: Compile every OD.
GLAS audit teams frequently work from Oracle's internal records, which may be incomplete — particularly for licences purchased through Oracle partners, inherited through acquisitions, or bundled with hardware. Missing ODs mean missing entitlements, which inflates audit findings. We routinely find $200K–$1M+ in
uncounted entitlements.
4What is the difference between a Processor licence and a Named User Plus licence?+
Processor: licensed by the number of processor cores running the Oracle programme, adjusted by Oracle's Core Factor Table (Intel/AMD = 0.5, most Oracle SPARC = 0.25–0.5).
Named User Plus (NUP): licensed by the number of individual humans (or non-human devices) that access the programme, with a minimum per-Processor floor (25 NUP per Processor for Database EE, 10 for Standard Edition 2). Processor licensing is simpler to administer but more expensive at small scale; NUP is cheaper for low-user-count environments but introduces counting complexity.
Commercial reality: Most compliance exposure comes from Processor licensing — specifically, how processors are counted in virtualised environments (VMware, Hyper-V, Nutanix). If you run Oracle on VMware, read
Database Licensing in Virtualised Environments before your next Oracle interaction. The answer to "how many Processors do I need to license?" can vary by 300% depending on interpretation.
5What is the Oracle Core Factor Table?+
A multiplier Oracle applies to physical cores to determine the licence count. Intel and AMD cores use a factor of 0.5 (so a 16-core server = 8 Processor licences). Oracle SPARC cores use 0.25–0.5. The Core Factor Table is an Oracle policy document, not a contractual term in your OLSA.
Commercial reality: The Core Factor Table does not apply in Oracle Cloud Infrastructure (OCI) — OCI uses OCPU or vCPU counting, which follows different rules. It also does not apply to NUP minimum calculations in the same way. And critically, because it is a policy (not a contract), Oracle can change it unilaterally. Organisations that negotiate Core Factor protections into their Ordering Documents gain certainty that others lack.
6What is Oracle Database Standard Edition 2, and when does it make sense?+
Oracle Database SE2 ($17,500/Processor, $350/NUP) is Oracle's lower-cost database tier, limited to servers with a maximum of 2 sockets and 16 threads. It lacks Enterprise Edition features like RAC (beyond basic failover), partitioning, and most management packs.
Commercial reality: SE2 is a pricing trap for growing workloads. The moment you exceed 2 sockets or 16 threads, you must upgrade to Enterprise Edition — where the price nearly triples ($47,500/Processor) and the required options (RAC, Advanced Security, Diagnostics Pack) can add another 50–100%. Before upgrading to EE, evaluate
PostgreSQL or cloud-native alternatives.
7What is a ULA, and is it a good deal?+
An Unlimited License Agreement gives you unlimited deployment rights for specified Oracle products during a 3–5 year term, for a fixed annual fee. At the end of the term, you "certify" — declaring your deployed quantities, which become your perpetual entitlement.
Commercial reality: A ULA is Oracle's most powerful commercial instrument. It solves your compliance problem today but creates dependency: Oracle's account team will push renewal (not certification) because each renewal grows the fee base 10–25%. The best outcome for most organisations is
certification — converting unlimited rights into fixed, owned entitlements that eliminate the ULA premium forever. Begin preparation 12 months before expiry. See
ULA vs PULA: The Two Models.
8What is a PULA?+
A Perpetual Unlimited License Agreement provides unlimited deployment rights with no expiry date and no certification requirement. You pay a fixed annual support fee ($2M–$10M+ depending on product scope) indefinitely.
Commercial reality: A PULA eliminates certification risk and audit exposure for the covered products — permanently. But it also locks you into a perpetual support obligation with annual uplift. The question is whether the certainty and risk elimination justify the premium over a well-executed
ULA certification. For organisations with high Oracle growth and high compliance complexity, a PULA can be the optimal structure. For stable environments, certification plus targeted purchases is usually cheaper.
9What is the CSI number?+
The Customer Support Identifier is Oracle's unique tracking number for your support entitlements. Every support request is filed against a CSI. Oracle tracks your entire licensed estate through CSI numbers.
Commercial reality: Organisations that have grown through M&A often have multiple CSI numbers — each associated with a different legal entity or acquisition. This creates fragmented visibility into your total entitlements and makes
audit defence harder. Consolidating CSI numbers (or at least maintaining a master register) is essential preparation for any Oracle commercial event.
10Where can I find Oracle's current price list?+
Oracle publishes its Technology and Applications price lists at
oracle.com. The Technology list covers Database, Middleware, and Java. The Applications list covers EBS, PeopleSoft, JD Edwards, and Fusion/Cloud.
Commercial reality: Nobody pays list price. Achievable discounts range from 30% (low leverage, small deal) to 55%+ (competitive alternatives, Q4 timing, large commitment). The list price matters primarily as the basis for your 22% annual support fee — a deeper discount on the initial purchase reduces your support obligation for the life of the licence. See
Oracle Price List 2026 and
Pricing Benchmarks.
Metrics, Counting, and Virtualisation: Questions 11–20
These questions arise when you attempt to count your Oracle deployments — and discover that the answer depends heavily on interpretation, infrastructure choices, and Oracle's own policy positions.
11How do I license Oracle on VMware?+
Oracle's position: VMware is "soft partitioning" — licence all physical cores on all hosts in the VMware cluster where Oracle could potentially run, not just the host currently running the Oracle VM. A 6-host, 120-core cluster = 60 Processor licences at 0.5 Core Factor, even if Oracle runs on one VM on one host.
Commercial reality: This is the single largest source of audit exposure in enterprise Oracle licensing. Oracle's position is a licensing policy, not a contractual term. Technical controls (DRS affinity rules, dedicated clusters) can reduce the claim. Independent advisory on this question alone has generated savings of $1M–$20M+ for individual organisations. See
Virtualisation Licensing Guide and
Partitioning Policy vs Contract.
12What is hard partitioning vs soft partitioning?+
Hard partitioning technologies (Oracle VM, Solaris Zones, IBM LPAR, certain VMware configurations) allow you to license only the cores assigned to the Oracle partition.
Soft partitioning technologies (VMware vSphere, Hyper-V, Nutanix AHV) — per Oracle's policy — require licensing all physical cores in the cluster.
Commercial reality: Oracle's hard/soft partitioning distinction is published in Oracle's own policy document, which Oracle can update unilaterally. The policy is not incorporated by reference into most OLSAs. This creates a grey area that benefits whoever prepares better for the argument. If you run Oracle on "soft" partitioned infrastructure, your options are: migrate to hard partitioning, negotiate contract language that overrides the policy, or prepare robust technical documentation to defend your position in an audit.
13How do I license Oracle in AWS or Azure?+
Oracle publishes an "Authorised Cloud Environment" policy for AWS, Azure, and GCP. For most standard instances: 2 vCPUs = 1 Processor licence (Intel). Dedicated tenancy or specific instance types qualify under this policy. BYOL allows you to use existing on-premise licences in the cloud.
Commercial reality: The Authorised Cloud policy is more favourable than Oracle's VMware position, but introduces new traps. BYOL licences cannot simultaneously count toward on-premise and cloud deployments — creating compliance gaps during migration. Oracle licensing on AWS/Azure is typically 2–3× more expensive than the same workload on OCI (where BYOL rules are more generous). See
OCI vs AWS for Oracle Workloads.
14Do I need to license Oracle Database options separately?+
Yes. Features like Real Application Clusters (RAC), Advanced Security, Partitioning, Diagnostics Pack, and Tuning Pack are separately priced options on top of the Database EE licence. Each option is licensed on the same metric (Processor or NUP) as the base database.
Commercial reality: The "real" cost of Oracle Database EE is not $47,500/Processor — it is $47,500 plus every option you need. A typical production deployment with RAC, Advanced Security, Diagnostics Pack, and Tuning Pack costs $80,000–$120,000 per Processor at list. Oracle's audit scripts specifically detect option usage, and
Advanced Security (TDE) and
Diagnostics/Tuning Pack (AWR) are the two fastest-growing audit findings in 2025–2026.
15What is the Employee metric, and which products use it?+
The
Employee metric counts every full-time, part-time, and temporary employee in your organisation — regardless of whether they use the Oracle software. It is used primarily for Oracle HCM Cloud (Hosted Employee) and
Java SE Universal Subscription. The metric reflects your total headcount, not your Oracle user count.
Commercial reality: The Employee metric is the most controversial pricing model in enterprise software. For Java SE, a 15,000-employee company pays approximately $945K/year at list — even if only 50 developers actually use Java. For HCM Cloud, every HR record counts including contractors, contingent workers, and pre-hires, creating a 2–5× cost difference versus Named User metrics. Negotiating the definition of "employee" and the measurement mechanism is the single most valuable lever in any Employee-metric deal. See
Java SE Cost Calculator.
16How does Oracle count processors in a container or Kubernetes environment?+
Oracle treats containers (Docker, Kubernetes, OpenShift) the same as VMware — as soft partitioning. Oracle's position: licence all physical cores on all hosts where the container orchestrator could schedule an Oracle workload.
Commercial reality: This position makes running Oracle in Kubernetes extremely expensive, because Kubernetes clusters are designed for workload mobility across all nodes. The practical mitigation: dedicate specific nodes to Oracle workloads using node affinity/tainting and document these controls thoroughly. Alternatively, run Oracle Database in OCI where container licensing follows OCI rules rather than the soft partitioning policy.
17Do I need a separate licence for disaster recovery?+
Oracle's standard position: DR environments running Oracle require full Processor licensing. However, Oracle's "Failover" policy allows up to 10 days of unlicensed DR operation per year for on-premise environments.
Commercial reality: The 10-day failover allowance is Oracle's policy position, not a contractual right in most OLSAs. If DR is critical to your architecture, negotiate explicit DR rights in your Ordering Document — specifying unlimited failover, warm standby, or active-passive configurations without additional licensing. This is routinely achievable in larger deals and eliminates a significant compliance grey area.
18Does Oracle WebLogic come with E-Business Suite or PeopleSoft?+
Oracle applications that include WebLogic as a component (EBS, PeopleSoft, Fusion Middleware) include a restricted-use WebLogic entitlement — but only for supporting the specific application. Using WebLogic outside the application's scope (for custom applications, other middleware, or integration) requires a separate WebLogic licence.
Commercial reality: WebLogic is one of Oracle's most commonly under-licensed products. Application installers deploy WebLogic automatically, and DBAs or developers often use it for purposes beyond the restricted entitlement without realising the licensing implications. GLAS scripts detect every WebLogic instance. Verify your
WebLogic entitlement before your next audit interaction.
19What is the Multitenant option, and when do I need it?+
Oracle Database 21c+ requires the Container Database (CDB) architecture. Every database runs in multitenant mode. Oracle allows up to 3 Pluggable Databases (PDBs) per CDB without a Multitenant licence. The 4th PDB triggers a licensing requirement at $17,500/Processor.
Commercial reality: Organisations consolidating databases onto fewer servers frequently exceed the 3-PDB threshold — creating unexpected licensing obligations that can negate the consolidation savings. Count your PDBs per CDB carefully before any database consolidation project. See the
2026 Price List analysis for the restructured Multitenant terms.
20What does "installed and/or running" mean for licensing purposes?+
Oracle's OLSA requires licences for programmes that are "installed and/or running." GLAS interprets this broadly: if Oracle software is installed on a server, it requires a licence — regardless of active usage.
Commercial reality: The phrase "and/or" is Oracle's advantage. Challenge it on a case-by-case basis: a product installed by default as part of an application stack, never configured, never accessed, and generating no data is not "running" in any meaningful sense. Document cases of default/unintentional installation carefully — this argument alone removes 10–20% of audit findings in our experience.
Audits and Compliance: Questions 21–30
These questions become urgent the moment Oracle sends an audit letter — or ideally, 12 months before that happens.
21Can Oracle audit me?+
Almost certainly yes. Your OLSA (typically Section 10) grants Oracle the right to verify compliance, usually with 45 days' notice. Refusing to cooperate is a contractual breach.
Commercial reality: You cannot refuse an audit — but you can manage it. You control the scope (which products, which environments), the timeline (negotiate extensions if needed), and the response to findings (which are always negotiable). See
How to Fight an Oracle Audit Claim.
22Why does Oracle audit certain companies?+
Common audit triggers: declining or static Oracle support revenue, upcoming renewal events, M&A activity, known virtualised environments, reduced engagement with Oracle sales, and competitive evaluations (Workday, AWS, PostgreSQL).
Commercial reality: Audits are not random. They are strategically timed to maximise Oracle's commercial leverage — typically 6–12 months before a renewal, ULA expiry, or major procurement decision. The audit creates urgency and a compliance "debt" that Oracle's sales team uses to accelerate and enlarge deals. See
How Oracle Selects Audit Targets.
23Who is Oracle GLAS (formerly LMS)?+
Global Licensing and Advisory Services is Oracle's internal audit division. GLAS deploys data collection scripts, analyses deployment data, and produces compliance reports.
Commercial reality: GLAS is not a neutral auditor. It is a revenue function whose findings are shared with Oracle's sales organisation. GLAS findings are systematically calculated to maximise the compliance gap — using Oracle's most favourable interpretation of every rule. Independent review of GLAS findings reduces the stated gap by 30–60% on average.
24Do I have to run Oracle's audit scripts on every server?+
No. You are obligated to provide data within the scope of the audit as defined by your OLSA. GLAS routinely requests broader access than contractually required. You should review your OLSA's audit clause, agree on the scope formally with Oracle, and provide data only for the agreed-upon scope.
Commercial reality: Running GLAS scripts on servers outside the agreed audit scope gives Oracle free intelligence about your environment. Control the scope carefully — and always conduct an internal self-assessment before running GLAS scripts so you understand your compliance position before Oracle sees the data.
25Can I challenge Oracle's audit findings?+
Absolutely. GLAS findings are an opening position, not a final determination. Every finding can be challenged on technical grounds (incorrect counting, scope errors), contractual grounds (entitlements GLAS missed, policy vs contract arguments), or commercial grounds (resolution pricing).
Commercial reality: Organisations that accept GLAS findings without challenge pay 2–3× more than organisations that engage independent advisory. The most common successful challenges: virtualisation counting methodology (reduces Processor count), uncounted entitlements from M&A, non-production environment exclusions, and distinguishing "installed" from "actively used." See
How to Fight an Audit Claim.
26What happens if I am found non-compliant?+
Oracle requires you to become compliant — but you choose how. Options: purchase additional licences, uninstall Oracle from non-compliant environments, migrate to alternatives, or negotiate a commercial resolution (ULA, PULA, cloud migration).
Commercial reality: Oracle cannot issue an invoice. An audit finding is a claim, not a debt. You are entitled to negotiate the resolution — including the price, the commercial structure, and the timeline. Never accept resolution at list price; demand 30–55% discount and time the resolution to
Oracle's Q4 (March–May) for maximum discount authority.
27Should I conduct a self-assessment before Oracle audits me?+
Yes — this is the single most valuable proactive step. An internal self-assessment (ideally with independent advisory) reveals your compliance position, identifies shelfware, and prepares counter-arguments before Oracle's audit team sees your data.
Commercial reality: Organisations that self-assess before an audit typically resolve 60–80% faster and at 30–50% lower cost than organisations that react to GLAS findings. The self-assessment also identifies
support optimisation opportunities — shelfware and unused licences where you can reduce annual support spend.
28Can Oracle audit my cloud environments?+
If you are running Oracle software in AWS, Azure, GCP, or any non-OCI cloud under BYOL or standard licences — yes, your OLSA audit rights extend to those environments. OCI-native services (Autonomous Database, Fusion Cloud) are not subject to traditional audits because Oracle manages the licensing directly.
Commercial reality: Cloud migrations often create temporary compliance gaps — licences counted for on-premise are redeployed to cloud, but the on-premise instances are not yet decommissioned. During migration, you may briefly need licensing in both environments. Plan the decommissioning timeline carefully and document every migration step.
29What is the typical Oracle audit timeline?+
From notification to resolution: 3–6 months. Notification (week 1), scope agreement (weeks 2–4), data collection (weeks 4–8), GLAS analysis and preliminary findings (weeks 8–12), challenge and negotiation (weeks 12–20+).
Commercial reality: Oracle benefits from speed — urgency creates commercial pressure. You benefit from a measured pace that allows thorough preparation. Do not let Oracle's timeline dictate your response cadence. Request extensions if needed (they are routinely granted) and never rush to resolve under time pressure.
30Does an Oracle audit protect me from being audited again?+
No standard "audit cooldown" exists in Oracle's OLSA. However, you can negotiate audit frequency limitations (e.g., no more than once every 2 or 3 years) as part of a resolution or renewal agreement.
Commercial reality: If you are resolving an audit through a commercial settlement, demand audit protection terms as part of the resolution: minimum 24–36 months before next audit, advance notification requirements, and limitations on audit scope. These protections cost Oracle nothing commercially but are valuable to you. Organisations that do not request them are audited again within 18–24 months.
Need Expert Oracle Licensing Guidance?
Redress Compliance provides independent Oracle licensing advisory services — fixed-fee, no vendor affiliations. Our specialists have helped enterprises save millions through strategic license optimization, audit defense, and contract negotiation.
Explore Oracle Advisory Services →
Support, Renewals, and Cost Management: Questions 31–37
Support costs represent the largest recurring Oracle expense — and the area where most organisations have the greatest untapped savings opportunity.
31How much does Oracle support cost?+
22% of the Net Licence Fee per year — the non-negotiable rate. But the base on which 22% is calculated is determined by your original purchase discount. A 50% discount on a $1M list = $500K NLF = $110K/year support. A 30% discount = $700K NLF = $154K/year — $44K more per year, forever.
Commercial reality: The most important number in your Oracle relationship is not the licence discount — it is the resulting Net Licence Fee that determines your perpetual support obligation. A deeper initial discount saves far more in cumulative support than it saves on the one-time licence purchase. Negotiate accordingly.
32Can I negotiate the 22% support rate?+
The 22% rate itself is essentially non-negotiable. However, you can negotiate the base (deeper licence discount = lower NLF = lower support), the annual uplift (negotiate to 0% or cap at CPI), and the scope (remove shelfware, true-down unused licences).
Commercial reality: The annual support uplift of 3–4% is where most overpayment accumulates. A 4% uplift on $1M support adds $480K in cumulative additional cost over 10 years. Negotiating 0% uplift is achievable with adequate leverage (competitive alternatives, support termination threat, large cloud commitment). This single negotiation point is worth more than most licence discount improvements.
33Can I drop Oracle support?+
Yes. You retain your perpetual licence even without support — but you lose access to patches, updates, and Oracle's support organisation. The reinstatement penalty if you resume later: all back-support fees plus 150% of those fees.
Commercial reality: The reinstatement penalty makes support termination feel irreversible — which is Oracle's intent. But for stable, mature environments (EBS 12.2, PeopleSoft 9.2, databases not being upgraded),
third-party support saves 50% with comparable service quality. Even if you do not terminate, a documented third-party evaluation achieves 15–30% better renewal outcomes from Oracle. See
Technip Energies: €12M Saved.
34What is Sustaining Support, and should I worry about it?+
Sustaining Support is Oracle's final support tier: no new patches, no new security updates, access to previously released fixes only. You pay the same annual fee as Premier Support for a fraction of the service.
Commercial reality: Sustaining Support is the point at which
third-party support becomes unambiguously better value. You are paying full price for no new content. Evaluate alternatives aggressively when your product enters Sustaining — the economic case for staying on Oracle support at this stage is almost non-existent.
35What is shelfware, and how much am I paying for it?+
Shelfware is licensed Oracle software that is no longer deployed or used — but you continue paying 22% annual support. Typically 15–30% of an organisation's Oracle licensed products qualify as shelfware.
Commercial reality: On a $2M annual support bill, shelfware typically represents $300K–$600K in avoidable cost per year. Oracle will not proactively tell you which products are unused. Identifying and removing shelfware requires a thorough deployment inventory compared against your Ordering Document history. See
Support Optimisation Guide.
36What are true-down rights, and how do I get them?+
True-down rights allow you to reduce your licensed quantities (and corresponding support fees) if usage decreases. Oracle's standard contracts do not include true-down — you must negotiate it explicitly.
Commercial reality: Without true-down rights, you are locked into your current count regardless of usage changes. If you decommission 20% of your Oracle infrastructure, you still pay support on 100% of licences. Negotiate 15–20% annual true-down at every renewal. This is routinely achievable in mid-to-large deals and protects you from paying for capacity you no longer need.
37When is the best time to negotiate an Oracle renewal?+
Oracle's fiscal year ends May 31. Q4 (March–May) offers maximum discount authority. Begin internal preparation in Q3 (December–February) so you arrive at Q4 with benchmark data, competitive alternatives, and a defined negotiation position.
Commercial reality: Deals closed in Oracle Q4 achieve 10–20% deeper discounts than Q1 (June–August). On a $2M deal, that is $200K–$400K in additional savings — purely from timing. Maintain the credible option to defer: "If terms are not acceptable by May 31, we will revisit in Q1." Oracle's fear of losing the deal to the next fiscal year unlocks concessions unavailable at any other time. See
Oracle Sales Tactics 2026.
📊 Free Assessment Tool
Have more licensing questions specific to your environment? Our free audit risk assessment analyzes your Oracle estate and highlights areas that need attention.
Take the Free Assessment →
Cloud, SaaS, and Java: Questions 38–44
These questions are dominating Oracle conversations in 2025–2026 as organisations navigate cloud migration pressure, Java enforcement escalation, and the shift from perpetual licences to subscription models.
38What are Oracle migration credits, and are they real?+
Migration credits are discretionary discounts Oracle offers to incentivise on-premise customers to move to Oracle Cloud. They are applied as subscription reductions, not cash. There is no published formula — credits are negotiated deal by deal.
Commercial reality: Credits are always available because Oracle needs migrations to meet cloud revenue targets. Never accept the first offer. Initial offers of 15–25% are standard; 30–50% is achievable with competitive alternatives and patience. Never tie credits to on-premise support termination dates — retain your perpetual licences as fallback. See
On-Premise to Fusion Cloud Playbook.
39What is BYOL (Bring Your Own License) to OCI?+
BYOL allows you to use on-premise Oracle licences in OCI to reduce
cloud subscription costs — typically 30–40% cheaper than licence-included OCI pricing. Licences must be current on support. Conversion ratios differ from on-premise counting.
Commercial reality: BYOL creates a compliance trap: the same licence cannot simultaneously count toward on-premise and OCI deployment. During migration, ensure that on-premise instances are decommissioned before counting those licences as BYOL in OCI. Oracle's audit scripts will check both environments.
40Is PeopleSoft or E-Business Suite going end-of-life?+
No. PeopleSoft 9.2 has no announced Premier Support end date. EBS 12.2 has Premier Support through 2032+. JD Edwards 9.2 has similarly extended support. Oracle's sales team may position migration as urgent — it is not.
Commercial reality: Oracle's revenue strategy for on-premise applications is not to raise prices but to create migration pressure through support lifecycle narratives and cloud migration incentives. Check your specific product version's support timeline on Oracle's support portal — the urgency Oracle presents may not match reality. See
PeopleSoft to HCM Cloud Migration Guide.
41Do I need an Oracle Java SE licence?+
Only if you are running Oracle's JDK distribution (not OpenJDK) on versions subject to the commercial licence: Java SE 8 (Update 211+), Java 11+, 17+, and 21+. Amazon Corretto, Eclipse Temurin, Azul Zulu, and other OpenJDK distributions are functionally identical and licence-free.
Commercial reality: Java is Oracle's fastest-growing compliance revenue stream. The per-employee metric (since January 2023) creates six- and seven-figure exposure from minimal usage. If you receive a
Java compliance letter, do not panic: verify versions, identify OpenJDK alternatives, protect your legacy metric if applicable, and negotiate aggressively. See
Java SE Pricing & Negotiation and
OpenJDK Alternatives.
42Can I switch from Oracle JDK to OpenJDK to avoid licensing?+
Yes. OpenJDK distributions (Corretto, Temurin, Azul) are functionally identical to Oracle JDK and are free. Migration is straightforward for most applications: replace the Oracle JDK installation with the OpenJDK distribution and test thoroughly.
Commercial reality: The credible threat of OpenJDK migration is your strongest Java negotiation lever — even if you do not ultimately migrate every installation. A documented migration plan with timeline and pilot results achieves 40–60% discounts on the Java SE Universal Subscription. See
Exiting Oracle Java SE.
43What happens to my data if I leave Oracle Cloud?+
Oracle's standard SaaS terms provide a 60-day data export window after subscription termination. After 60 days, your data is deleted.
Commercial reality: 60 days is insufficient for complex enterprise data migration. Negotiate: 180-day export window, defined export formats (CSV/XML, not Oracle-proprietary), continued read-only access during the export period, and assistance with data mapping. These terms are achievable and essential for de-risking any Oracle Cloud commitment.
44What are Oracle Universal Credits (OCI)?+
A pre-purchased credit pool you consume against OCI services. Credits expire at term end — unused credits are forfeited. Oracle sells Universal Credits as annual commitments with defined consumption rates per service.
Commercial reality: The trap: Oracle sizes initial credit commitments based on projected consumption that often exceeds actual usage. You over-purchase, under-consume, and forfeit credits. Negotiate: credit rollover provisions, annual true-down rights, flexible cross-service allocation, and the right to reduce commitment at renewal. See
OCI vs AWS Analysis.
Strategy and Negotiation: Questions 45–50
These are the questions that separate organisations paying $3M per year from organisations paying $1.5M for the same Oracle capability.
45How much discount can I get off Oracle's list price?+
Achievable discounts by product: Database EE 35–55%, Applications 30–45%, Middleware 30–50%, Java SE 40–60%, Cloud/SaaS 25–50%. The range depends on deal size, timing, competitive leverage, and negotiation skill.
Commercial reality: The single most important factor is a credible competitive alternative — not the size of the deal. Oracle's deal desk has maximum flexibility when a customer presents a documented evaluation of Workday, PostgreSQL, AWS, or OpenJDK. A $500K deal with strong competitive leverage achieves deeper discounts than a $5M deal with no alternatives. See
Pricing Benchmarks.
46Should I certify or renew my ULA?+
In most cases, certify. Certification converts unlimited rights into fixed, owned perpetual entitlements — eliminating the ULA premium and stopping the dependency cycle. Renewal makes sense only if you have genuine, continued growth in Oracle deployments that would exceed your certified entitlement within the next term.
Commercial reality: Oracle's account team will always push renewal because it grows revenue. Over two renewal cycles, ULA fees typically double from the original agreement. Certification requires thorough preparation (12 months in advance) but permanently breaks the ULA cost cycle. See
ULA vs PULA Guide and
ULA Certification Case Study.
47How do I prepare for an Oracle negotiation?+
Five essentials: (1) Complete deployment inventory — know what you have before Oracle tells you. (2) Benchmark data — know what comparable organisations pay. (3) Competitive alternatives — documented evaluations, not casual mentions. (4) Clear internal alignment — procurement leads commercial, IT leads technical. (5) Timeline discipline — align to Oracle Q4 but maintain the option to defer.
Commercial reality: The number one predictor of Oracle negotiation outcomes is preparation depth. Organisations that invest 4–6 weeks in preparation achieve 20–40% better outcomes than organisations that react to Oracle's proposals. See
Oracle Vendor Management Guide.
48Should I use third-party support for Oracle?+
For stable, mature environments (EBS, PeopleSoft, databases not being upgraded): the economic case is strong — 50% annual savings with comparable service quality from providers like Rimini Street or Spinnaker Support. For environments requiring new patches, version upgrades, or cloud migration: retain Oracle Premier Support.
Commercial reality: Even if you do not switch, a documented third-party evaluation achieves 15–30% better renewal terms from Oracle. Oracle's $8B+ support revenue at 90%+ margins means every dollar you threaten to redirect is acutely motivating. The evaluation costs nothing; the leverage it creates is significant. See
Third-Party vs Oracle Premier Support.
49Do I need an independent Oracle licensing advisor?+
For any Oracle interaction with six-figure financial implications — audit, renewal, ULA decision, cloud migration, Java compliance — independent advisory typically generates 5–50× ROI. Advisory fees of $50K–$150K routinely produce savings of $500K–$10M+.
Commercial reality: "Independent" means no Oracle commercial relationship — no partnerships, no referral fees, no implementation revenue. Oracle's own partners and Customer Success team are measured on account growth, which means their advice carries an implicit commercial dimension. The only source of genuinely aligned advice is an advisor whose sole revenue comes from your engagement, not Oracle's.
50What is the single most important thing I should do about Oracle licensing right now?+
Know your position. Compile your complete Ordering Document history, inventory your deployed Oracle products (including
Database options, Java installations, and WebLogic instances), identify shelfware, and understand your virtualisation exposure. Every Oracle commercial interaction — audit, renewal, migration, expansion — starts with the question "what do you have?" The organisation that knows the answer controls the conversation.
Commercial reality: Most organisations cannot answer this question accurately. That asymmetry is Oracle's greatest commercial advantage. The investment in understanding your own position — before Oracle asks — is the highest-ROI activity in enterprise software
licensing management. It costs less than any single Oracle audit finding and protects against every future one.
Book a confidential consultation to start.