How to Use This Assessment

This tool is structured around the same 20 risk vectors Redress Compliance reviews in every Oracle estate engagement. Each item includes an expert note drawn from real audit findings, ULA certifications, Java SE remediation projects, and Oracle negotiation outcomes across the energy sector. Work through each point methodically. Any item where your answer is "unsure" or "no" represents a live financial or compliance exposure.

For this engagement, the estate covered Oracle Database Enterprise Edition, Oracle E-Business Suite, Oracle Primavera P6 EPPM, Oracle WebLogic Server, Oracle Java SE across tens of thousands of employee endpoints, and extensive middleware running on a VMware vSphere infrastructure distributed across multiple continents. The majority of the $22M saving came from six of the 20 items below — four of which are consistently the highest-value findings in global energy sector Oracle audits.

"When an oilfield services company grows by acquisition — as most of them do — the Oracle estate grows too, silently, in ways that no internal team is tracking. By the time Oracle's LMS team shows up, the exposure has been accumulating for years."
— Fredrik Filipsson, Redress Compliance

Section 1: Oracle Database Licensing Fundamentals

Oracle Database Enterprise Edition remains the highest-risk product in most energy sector estates. Processor licensing, core factors, and inadvertent options/packs activation together account for the majority of Oracle audit findings. Global oilfield services companies typically run Oracle DB across large x86 server clusters at multiple facilities worldwide — making every calculation in this section extremely high-stakes.

01 Processor Licence Count vs. Deployed Physical Cores HIGH RISK

Confirm that your Oracle Database processor licence count equals the total physical cores on every server running Oracle software, multiplied by the applicable core factor from Oracle's Processor Core Factor Table. Intel Xeon and AMD EPYC processors typically carry a 0.5 factor; IBM POWER carries 1.0. Verify the exact processor model in each server, apply the correct factor, and round up to the nearest whole number. Compare against every current entitlement in your licence portfolio.

Expert NoteIn this engagement, seven server clusters across four continents had been subject to hardware refreshes — from older Intel Xeon E5 processors to Intel Xeon Scalable — without any corresponding licence review. Even though both processor generations carry the same 0.5 core factor, the new hardware had significantly higher core counts per socket. The result was a 47-processor licence shortfall that, at Oracle's annual support rate alone, represented $2.1M in overstated support spend on entitlements the company no longer held. Recovering this entitlement reconciliation was the first and largest item addressed.
02 Database Options & Packs — Active Feature Usage Audit HIGH RISK

Oracle installs all options and management packs alongside Database Enterprise Edition by default. Any feature used — even once, even unintentionally by a DBA running a routine diagnostic — is treated as licensed and creates a perpetual obligation. Run Oracle's Feature Usage Statistics view (DBA_FEATURE_USAGE_STATISTICS) across all database instances. Map every feature where CURRENTLY_USED = TRUE or DETECTED_USAGES > 0 to a specific licence entitlement. Common unlicensed features found in energy and manufacturing Oracle estates include Diagnostic Pack, Tuning Pack, Advanced Compression, Active Data Guard, Oracle Partitioning, and the Real Application Testing option.

Expert NoteAcross 23 production Oracle Database instances in this engagement, Diagnostic Pack and Tuning Pack were active on 18 of them. Neither was licensed. Oracle's internal assessment flagged this as a $4.8M finding. Redress Compliance successfully argued that usage had been accidental — triggered by a monitoring tool that queried AWR views automatically — that it had been immediately ceased, and that Oracle's own installation defaults had not adequately disclosed the licensing risk at the point of setup. The finding was settled at zero additional licence cost. This outcome is not guaranteed; it depends on the documentation trail and how quickly usage is ceased once discovered.
03 Named User Plus Minimums — Per-Processor Floor Check MEDIUM RISK

If any Oracle Database instances are licensed on a Named User Plus (NUP) metric, Oracle requires a minimum of 25 NUPs per processor licence (calculated using the core factor method). Validate that your NUP count meets this floor on every NUP-licensed server. This minimum is frequently violated when processor counts change following hardware refreshes, virtualisation migrations, or server consolidations — none of which typically trigger a licence review in organisations without a mature SAM programme.

Expert NoteNUP minimum violations are almost always inadvertent. In oilfield services environments, Oracle databases are sometimes deployed to serve operational systems — production scheduling, drilling engineering tools, logistics platforms — by teams who have no visibility of licence metrics or floor calculations. In this engagement, four systems licensed on NUP had fallen below the minimum following infrastructure consolidation. Remediating the shortfall cost less than $180K — identified and closed before Oracle's audit team arrived.
04 Disaster Recovery & High-Availability Licensing HIGH RISK

Oracle requires DR and standby database servers running Oracle software to be licensed, unless a specific licensing exception applies. The Active Data Guard option — required for any reporting workload on a standby — must be separately licensed. Passive failover configurations may qualify for Oracle's 10-day DR policy, but only if precise conditions are met, documented, and maintained. Inventory every DR and HA database instance and validate which policy governs each one.

Expert NoteThe DR licensing position was the most contentious item in this engagement. The company had deployed Oracle Data Guard in active-reporting mode on standby databases to support operational dashboards for drilling operations. This constitutes use of the Active Data Guard option, which was not licensed. Separately, one RAC cluster used for high-availability production operations required Real Application Clusters licences on all nodes — a requirement not captured in the entitlement register. Together, these items represented $3.1M in exposure before remediation.

Section 2: Virtualisation & Infrastructure Risk

Oracle's virtualisation licensing policy is the single most contentious and financially significant risk area for energy companies running modern IT infrastructure. Oracle does not recognise VMware vSphere, Microsoft Hyper-V, or most third-party hypervisors as "hard partitioning" — meaning that Oracle software deployable on any host in a cluster creates licensing obligations across the entire cluster, regardless of where the software actually runs.

05 VMware Cluster-Wide Licensing Exposure HIGH RISK

If Oracle Database or Middleware VMs are hosted in a VMware vSphere cluster, Oracle's licensing position requires all physical hosts in that cluster to be fully licensed — not just the hosts where Oracle VMs currently reside. Identify every VMware cluster hosting Oracle workloads. Count the total physical cores across all hosts in each cluster, apply the appropriate core factors, and compare the result against current entitlements. If you have not performed this calculation recently, assume you are materially under-licensed.

Expert NoteThis was the single largest exposure area in the engagement — and the most commercially significant to resolve. Oracle Database VMs were deployed across a 22-host VMware cluster at the primary US data centre. The company had licensed only the 6 hosts the Oracle VMs were pinned to using affinity rules. Oracle's position was that all 22 hosts required full licensing. At 32 cores per host and a 0.5 Intel core factor, this created an exposure of 256 unlicensed processor licences — valued at approximately $12.2M at Oracle's then-current list pricing. Redress Compliance eliminated the exposure entirely by engineering a migration to dedicated bare-metal servers for the highest-risk Oracle DB instances, removing them from the shared VMware cluster and closing the cluster-wide obligation without purchasing a single additional licence.
06 VM Mobility, DRS Automation, and Live Migration Audit HIGH RISK

Any Oracle VM that has the potential to migrate — via VMware vMotion, DRS, or automated load-balancing — to an unlicensed host creates an immediate compliance exposure. Oracle's LMS audit scripts capture vCenter migration logs. Even historical vMotion events triggered by maintenance operations can be used to assert licensing obligations across destination hosts and their clusters. Disable automated DRS migration for all Oracle VMs. Document and enforce VM affinity rules. Audit all vMotion history for Oracle instances.

Expert NoteOracle's audit teams routinely request vCenter event logs covering the preceding 24 months. In this engagement, automated DRS had triggered 14 vMotion events for Oracle DB VMs over an 8-month period — each one potentially extending licensing obligations to additional hosts. Redress Compliance successfully argued that these migrations were involuntary and immediately mitigated once the policy was corrected. Organisations without this documentation are in a materially weaker negotiating position: Oracle will argue that every destination host in every migration event must be licensed retroactively.
07 Hard Partitioning Alternatives and Infrastructure Roadmap MEDIUM RISK

Oracle recognises only a narrow set of technologies as "hard partitioning" that limits Oracle licensing to a subset of a physical server. These include Oracle VM Server for x86 (with CPU pinning), Oracle Solaris Zones (capped), and IBM LPAR with dedicated CPUs. If your organisation is evaluating a move away from VMware — a common consideration following Broadcom's 2024 VMware acquisition and aggressive licensing changes — assess whether migrating Oracle workloads to dedicated bare metal or OCI eliminates the cluster-wide soft-partitioning risk permanently.

Expert NoteThe Broadcom/VMware acquisition created a strategic inflection point for Oracle licensing. Enterprises renegotiating VMware contracts are simultaneously the ideal time to rationalise Oracle workload placement. For this client, migrating the eight highest-risk Oracle DB instances to dedicated bare-metal servers in the primary US data centre eliminated the VMware cluster-wide exposure entirely. The migration cost was recovered within the first year through the elimination of unnecessary Oracle support spend on excess entitlements.
Get the full Oracle Licensing Audit Defence Kit
Templates, scripts, and negotiation frameworks for energy sector Oracle audits
Download Free

Section 3: Oracle Applications & Middleware Licensing

Oracle's application portfolio — including E-Business Suite, Primavera P6 EPPM, and WebLogic Server — carries licensing complexity that is distinct from database licensing. User count accuracy, role-based licence type mapping, and integration topology all generate significant audit exposure in global manufacturing and oilfield services organisations.

08 Oracle E-Business Suite — User Count and Licence Type Accuracy HIGH RISK

Oracle EBS is licensed on a Named User Plus metric for most modules. Validate that every active user account corresponds to a licenced named user — including service accounts, integration accounts, and external users accessing the system via APIs. Identify the precise licence type for each user based on the modules they access. EBS modules carry different per-user pricing; Finance and Procurement users require a higher licence type than limited-function users. Reconcile the licence type against actual module usage.

Expert NoteIn this engagement, the EBS user register had not been reconciled with the actual licence entitlement for over three years. Following multiple acquisitions, former employees of acquired entities had been migrated into the EBS instance without corresponding licence purchases. Additionally, 340 users classified as "limited" users were accessing Procurement and Supply Chain modules that required full Named User Plus licences. This discrepancy alone represented $1.4M in exposure — resolved through a combination of user deactivation and licence reclassification during the engagement period.
09 Oracle Primavera P6 EPPM — Licence Scope and Integration Topology MEDIUM RISK

Oracle Primavera P6 EPPM is licensed per named user. Validate that every individual — including project managers, schedulers, engineers, and read-only reviewers — who accesses the system holds a named user licence. Pay particular attention to the integration layer: if P6 is integrated with EBS or third-party systems via APIs, the API calling accounts may themselves require licensing. Confirm also that the P6 version in deployment is covered by your current support entitlement — organisations using older P6 versions on lapsed support are in an unsupported and unlicensed position.

Expert NotePrimavera P6 is pervasive in oilfield services organisations — it underpins project scheduling for multi-billion-dollar capital equipment programmes. In this engagement, P6 EPPM was integrated with Oracle EBS via a custom SOA integration layer. The integration user accounts had never been licensed. Additionally, 112 "view-only" schedulers at engineering facilities in multiple countries had access to P6 but were not reflected in the named user count. These two items together represented $620K in exposure — resolved through a negotiated licence true-up at significantly below Oracle's list price.
10 Oracle WebLogic Server — Deployment Topology and Edition Compliance HIGH RISK

Oracle WebLogic Server is licensed per processor using the same core-factor method as Oracle Database. If WebLogic is deployed in a VMware environment, the same cluster-wide licensing risk applies. Confirm the edition deployed (Standard, Enterprise, or Suite) and that the features in use are covered by that edition. WebLogic Enterprise features — including clustering, session replication, active grid link, and Oracle Coherence — require Enterprise Edition or Suite licensing; Standard Edition covers only basic application server functions.

Expert NoteWebLogic deployments are frequently overlooked in Oracle estate reviews because they are seen as "infrastructure" by application teams rather than licensed Oracle software. In this engagement, WebLogic Enterprise Edition features — specifically Oracle Coherence for in-memory data grid functionality — were active on Standard Edition licences across three middleware tiers. This misclassification represented $980K in additional licence exposure. The finding was mitigated by deactivating the specific Coherence features and validating the Standard Edition footprint before Oracle's audit script captured the usage data.
11 Third-Party and Internal Application Integrations — Technology Licence Obligations MEDIUM RISK

When third-party applications — ERP extensions, data integration tools, operational technology platforms — access Oracle Database, they may create additional Technology Licence obligations. Oracle's policy in some cases requires an additional "Application Specific Full Use" licence for third-party applications accessing Oracle DB. Review your integration architecture and confirm that every application touching Oracle DB is doing so within the scope of your existing Technology licences, or that an appropriate ASFU or other licence covers the integration.

Expert NoteIn the energy sector, this risk is acute because Oracle EBS or Database instances are routinely connected to operational technology systems — SCADA platforms, drilling data management tools, production scheduling systems — by engineering teams who have no awareness of Oracle's application integration licensing policies. In this engagement, two SCADA integration connectors were confirmed to be accessing Oracle DB outside the scope of Technology licences. Oracle's position was challenged successfully on the basis that the connectors were "report-only" access tools, reducing exposure from $760K to zero.

Section 4: Java SE Subscription Exposure

Oracle's 2023 Java SE licensing change — from per-processor/per-named-user to per-employee (Universal Subscription) — represents the most significant licensing risk change for large employers since Oracle's database processor metric was introduced. For a global oilfield services enterprise with 30,000+ employees, Java SE exposure under the new model can reach tens of millions of dollars annually. This section is critical.

12 Java SE Installation Discovery — Full Enterprise Footprint HIGH RISK

Oracle's Java SE Universal Subscription (introduced January 2023) is priced per employee of the entire organisation — not per installation, per user, or per server. If any Oracle Java SE installation exists anywhere in your estate, Oracle's position is that you owe subscriptions for every employee globally, including part-time workers. Conduct a comprehensive Java SE installation discovery across all servers, laptops, workstations, virtual machines, containers, and embedded systems. Identify every JDK and JRE version installed. Separate Oracle Java SE from OpenJDK and other free-distribution builds that do not trigger Oracle licensing obligations.

Expert NoteJava SE discovery in a 500-location global oilfield services company is a significant undertaking. In this engagement, Oracle Java SE was found on 4,200 endpoints — primarily on engineering workstations running legacy applications that had never been updated to OpenJDK builds. The remaining 95% of the estate was running either OpenJDK or had no Java installation. Oracle's position at the time of initial contact was that the entire global employee base — approximately 32,000 people — was subject to the Java SE Universal Subscription rate. Redress Compliance's engagement strategy reduced the billable scope to zero through a complete migration to OpenJDK across all affected endpoints prior to Oracle formalising its claim.
13 OpenJDK Migration Readiness and Application Compatibility MEDIUM RISK

OpenJDK — specifically Eclipse Temurin (Adoptium), Azul Zulu, Amazon Corretto, or Red Hat's OpenJDK build — is a fully standards-compliant, free-distribution alternative to Oracle Java SE that does not trigger Oracle licensing obligations. Assess your Java-dependent applications for OpenJDK compatibility. Most applications certified for Java 11 or Java 17 will run without modification on the corresponding OpenJDK build. Applications relying on Oracle-specific JVM extensions may require remediation. Develop and execute a migration plan before Oracle's audit team makes contact.

Expert NoteThe single most important action an organisation can take to reduce Java SE exposure is to complete an OpenJDK migration before Oracle's LMS team issues a formal audit notice. Once Oracle's audit process is initiated, the cost and time pressure of parallel remediation and negotiation increases substantially. In this engagement, the 12-week assessment included a parallel OpenJDK migration sprint for the 4,200 affected endpoints. By week 8, all Oracle Java SE installations had been replaced with Eclipse Temurin 17. Oracle's subsequent audit request was responded to with a clean discovery report showing zero Oracle Java SE instances — closing the exposure entirely.
14 Java SE ULA and Legacy Licence Entitlements — Prior Agreement Review MEDIUM RISK

Some organisations hold legacy Java SE perpetual licences or Java ULA agreements that predate Oracle's 2023 licensing model change. Review your Oracle contract portfolio for any Java SE-specific agreements. Confirm whether these agreements provide any protection against the employee-based subscription demand, what the certification terms are for any Java ULA in place, and whether Oracle's retroactive assertion of the Universal Subscription metric applies to existing agreements. Legal review of contract terms by specialist Oracle licence counsel is recommended before engaging Oracle on this point.

Expert NoteLegacy Java licence entitlements provide limited but potentially valuable protection in negotiation. In one instance during this engagement, a Java SE processor licence entitlement dating from 2018 was used to argue that Oracle's claim to enforce the employee-based subscription retroactively was inconsistent with the terms of the original agreement. While Oracle's position on this argument varies depending on the specific contract language, having documented entitlement history materially strengthens your negotiating position and slows Oracle's ability to enforce an immediate subscription demand.
Assess your Oracle Java SE exposure now
Free Oracle Licensing Assessment — no obligation, expert-led, results in 5 business days
Start Assessment

Section 5: ULA Strategy, Support Reduction & Remediation

For large Oracle customers, the Unlimited Licence Agreement is both a shield and a trap. Correctly structured and certified, a ULA can eliminate audit exposure for the products in scope. Poorly managed, it becomes a vehicle for Oracle to expand its revenue footprint at renewal. This final section covers ULA positioning, support cost reduction, and the remediation actions that generate the most durable savings.

15 Oracle ULA Scope Review — Products Covered and Certification Readiness HIGH RISK

If your organisation holds an Oracle Unlimited Licence Agreement, confirm the precise products included in scope. Oracle ULAs typically cover a named list of products — any deployment of Oracle software outside the scope list is not covered and creates separate exposure. Review the ULA certification date and process. At certification, you declare your full deployment of in-scope products, which Oracle converts to perpetual licences at that quantity. If you certify at a low deployment count, you lose the benefit of any headroom. If you have not modelled your optimal certification position, you are leaving value on the table.

Expert NoteULA certification strategy is one of the highest-value engagements Redress Compliance undertakes. In this engagement, an Oracle Database ULA was approaching certification. The client's internal team planned to certify at 180 processor licences — the count they believed accurately reflected current deployment. Redress Compliance's discovery identified an additional 94 processor licences of deployment that were legally in scope and should have been declared. Certifying at 274 processors instead of 180 locked in $4.2M of additional perpetual licence value that would have been permanently lost at certification.
16 ULA Renewal vs. Exit — Strategic Decision Framework MEDIUM RISK

At ULA expiry, organisations face a strategic decision: renew the ULA (accepting Oracle's proposed renewal terms), certify and exit the ULA (converting to perpetual licences), or use the leverage of the renewal decision to negotiate a broad restructuring of the Oracle relationship. Oracle's commercial team will strongly encourage renewal regardless of whether it serves your interests. Analyse your growth trajectory for ULA-covered products before the renewal window opens. If deployment is stable or declining, certification and exit may be the correct choice. If deployment is growing rapidly, renewal may preserve optionality.

Expert NoteOracle's renewal process begins, informally, 12–18 months before the ULA expiry date. Oracle account managers are incentivised to secure renewals early, before the customer has had time to conduct an independent analysis. In this engagement, Oracle had already presented a renewal proposal at a 22% uplift over the original ULA value. After independent analysis confirmed that the client's Oracle deployment was stable and not growing, Redress Compliance recommended certification and exit. The client exited the ULA with 274 processor licences of perpetual Database EE — a position worth significantly more commercially than the renewal Oracle was proposing.
17 Oracle Support Cost Review — 22% Annual Uplift and Termination Rights MEDIUM RISK

Oracle's standard annual support rate is 22% of the net licence value. This rate applies regardless of whether you use the support services — and Oracle has no contractual obligation to reduce it. However, you have the right to terminate support on products you no longer deploy or use. Conduct a full licence and support entitlement review to identify products for which support can be legitimately terminated. Review also whether third-party maintenance providers (Rimini Street, Spinnaker Support) are appropriate for legacy Oracle products where Oracle's support roadmap has ended.

Expert NoteSupport termination is frequently the fastest route to documented Oracle savings. In this engagement, 34 separate Oracle product entitlements were identified for which the client was paying annual support but which were either no longer deployed, had been superseded by a more recent version, or had been part of a divested business unit. Terminating support on these products reduced annual Oracle support spend by $1.6M — a saving that recurs every year without any renegotiation. The process requires careful documentation of the termination basis to avoid Oracle asserting that support-only termination leaves the perpetual licences in an unlicensed position.
18 Acquired Entity Oracle Estates — Post-M&A Licence Integration Risk HIGH RISK

Every acquisition creates an Oracle licensing event. When you acquire a company that runs Oracle software, you inherit its Oracle estate — including any compliance gaps, unlicensed deployments, or audit notices in progress. Oracle's change of control provisions allow Oracle to renegotiate support terms or assert that the acquired entity's licences do not transfer to the acquirer without Oracle's consent. Review every acquisition completed in the last five years for Oracle estate implications. Conduct a targeted Oracle assessment on any acquired entity with a significant Oracle footprint before Oracle's account team makes contact.

Expert NoteThe oilfield services sector is characterised by active M&A. In this engagement, the client had completed six acquisitions over three years. Three of the acquired entities had Oracle estates that had never been integrated into the client's licence management programme. One entity had an Oracle audit notice that had been unresponded to for 11 months — a serious escalation risk. Redress Compliance assessed and remediated all three acquired estates within the 12-week engagement period, closing the open audit notice through a negotiated settlement that was 73% below Oracle's initial demand.
19 Oracle Cloud Migration — On-Premises Licence Credit and BYOL Analysis LOW RISK

Oracle Bring Your Own Licence (BYOL) allows on-premises perpetual licences to be applied to Oracle Cloud Infrastructure (OCI) workloads, potentially eliminating or significantly reducing OCI compute costs for Oracle software. If your organisation is evaluating a move to cloud for Oracle workloads, conduct a BYOL analysis before committing to any OCI deal. Additionally, Oracle's support credits and migration incentive programmes can further reduce OCI costs for organisations with a large on-premises Oracle estate. Understand the full value of your existing licence portfolio before signing any OCI commitment.

Expert NoteBYOL on OCI is one of the few areas where Oracle's commercial model genuinely benefits the customer — provided the BYOL terms are correctly negotiated upfront. In this engagement, the client's 274 perpetual Database EE processor licences, once certified from the ULA, were assessed for OCI BYOL applicability. The analysis confirmed that migrating six non-critical Oracle DB workloads to OCI using BYOL would reduce OCI compute spend by approximately $380K annually compared to the standard OCI pricing for the equivalent licensed configuration.
20 Oracle Audit Readiness — Documentation, Evidence, and Response Protocol HIGH RISK

Oracle's LMS (License Management Services) audits are initiated by a formal written notice. From that point, Oracle controls the timeline, the scope, and the data collection methodology — unless you have independent expertise engaged to manage the process on your behalf. Ensure your organisation has a documented Oracle audit response protocol before an audit notice arrives. This should include: the internal escalation path (who is notified and who owns the response), the policy on what data Oracle is permitted to collect and through what mechanism, the engagement of independent Oracle licence specialists before any data is shared with Oracle, and the negotiation authority for any settlement.

Expert NoteThe most expensive Oracle audits are the ones where the customer responds directly to Oracle's LMS team without independent specialist support — providing LMS with uncontrolled access to discovery scripts, licence inventories, and deployment data before the compliance position has been independently assessed. In this engagement, the 12-week assessment concluded with a comprehensive audit readiness package: a clean, independently verified licence position, a structured Oracle data room for any future audit response, and a pre-agreed negotiation position covering all areas of residual exposure. When Oracle's account team made contact six weeks after the engagement closed, the client's response was immediate, confident, and grounded in a fully documented position. Oracle's informal audit enquiry was resolved without escalating to a formal LMS audit notice.

Closing Notes: What $22M in Oracle Savings Actually Looks Like

The $22M figure recovered in this engagement breaks down across six primary areas, each of which corresponds directly to items in this checklist. The largest single item — VMware cluster-wide exposure elimination at $12.2M — required no licence purchase: only independent technical analysis and a structured infrastructure change. The second-largest item — Oracle Database options/packs remediation at $4.8M — required only documentation and the immediate cessation of unlicensed feature usage. The Java SE migration, worth approximately $3.8M in avoided annual subscription cost, required a 12-week OpenJDK migration sprint. The remaining $1.2M came from EBS user reclassification, support termination, and negotiated settlement of the outstanding audit notice from an acquired entity.

The pattern across all these items is consistent with what Redress Compliance observes in every large Oracle estate engagement: the most significant savings do not come from negotiating better prices for licences you need. They come from eliminating obligations you were never required to hold — through independent analysis, precise technical remediation, and expert-led negotiation before Oracle's auditors define the scope.

"The best Oracle audit outcome is the one where Oracle's audit team never files a formal notice — because your compliance position is already documented, your remediation is already complete, and your negotiating team is already in place."
— Fredrik Filipsson, Redress Compliance
Request a confidential Oracle Licensing Assessment
We identify exposure, model remediation options, and deliver a clear action plan — in 5 business days.
Book a Call