Home›Training Academy›Oracle Licensing Mastery›Session 23
Oracle Licensing Mastery · Module 5 · Session 23 of 40 · 28:54

The common findings

The audit findings report writes itself, assembled from five standard claim families: VMware and the policy paper that no contract incorporates, options and packs flagged by usage data that overcounts by design, disaster recovery estates where noise and genuine exposure share a report line, named user arithmetic inflated by departed accounts, and Java priced on the employee metric. This session teaches each claim, its honest core, and its written challenge, then grades session 21's $4.2M preliminary finding line by line until $2.4M collapses on evidence, $600K on its own data, and $1.2M walks forward as the settlement baseline.

What you will be able to do after this session

  • 1Predict the report. Know the five findings that fill nearly every Oracle audit before it arrives.
  • 2Argue VMware. Separate the contract's counting rule from the policy paper's, and challenge accordingly.
  • 3Kill false positives. Read options and pack claims against actual usage evidence, not feature flags.
  • 4Sort the DR claims. Know which standby topologies genuinely need licenses and which do not.
  • 5Grade every claim. Sort a findings report into challengeable, negotiable, and genuine, before responding.

How the session works

A taught session with three knowledge checks: the $2.1M whole vCenter VMware claim collapsed to the contained cluster on contract language, the three year old Tuning Pack upgrade artifact withdrawn on its own usage history, and the graded report answered with challenges, struck noise, and a held baseline. It closes with the $4.2M preliminary finding dissected line by line into the $1.2M that actually enters settlement.

Homework before the next session, about one hour

  • 1Audit your own estate. Run the five findings against yourself: VMware containment, options flags, DR topology, user counts, Java inventory.
  • 2Check the containment. Where does Oracle actually run in your virtual estate, and what evidence proves the boundary?
  • 3Pull the feature stats. One production database's feature usage view, read with the artifact test.
  • 4Map the DR posture. Every standby labeled backup, failover, or active. The active ones need licenses or a risk register entry.
  • 5Refresh one user count. Your largest NUP system: current access list against licenses held, departed users flagged.
Learning the playbook and want it applied to your numbers? We work on contingency: 25% of what we save you. Nothing saved, nothing paid.
Review my deal