Home›Training Academy›Oracle Licensing Mastery›Session 30
Oracle Licensing Mastery · Module 6 · Session 30 of 40 · 30:17

Exadata, Cloud at Customer, and dedicated regions

Module 6's synthesis: the constructs between datacenter and cloud. Exadata is the most license dense hardware Oracle sells, and Capacity on Demand plus the core factor keep it affordable, license the activated cores, not the installed ones. The same machine comes four ways, owned, Cloud at Customer, Exadata Cloud Service, and Dedicated Region, and the construct is chosen by the binding constraint, residency, latency, sovereignty, elasticity, or cost, with BYOL carrying licenses across all of them. This session places a whole estate across the spectrum, from owned iron to public cloud, and closes the cloud module.

What you will be able to do after this session

  • 1License Exadata. Count the database and options on an engineered system, capacity on demand included.
  • 2Read the four flavors. Tell owned, Cloud at Customer, Exadata Cloud Service, and Dedicated Region apart, commercially.
  • 3Price Cloud at Customer. Understand the consumption model on hardware in your own datacenter, BYOL and all.
  • 4Weigh dedicated regions. Know when a full OCI region in your building is the answer, and when it is overkill.
  • 5Close the module. Place every workload on the datacenter to cloud spectrum with the counting for each.

How the session works

A taught session with three knowledge checks: the 48 core Exadata licensed at 8 for its 16 activated cores under Capacity on Demand, the residency bound bank routed to Cloud at Customer, and the elastic dev/test job kept off a committed on premises construct. It closes with one estate placed across five constructs, each chosen by its binding constraint, supplied by one BYOL license pool.

Homework before the next session, about one hour

  • 1Audit the Exadata. Installed cores versus activated cores versus licenses held. Capacity on Demand configured, or paying for dark cores?
  • 2Inventory the options. On each engineered system: which options and packs are enabled, and are they all entitled?
  • 3Name the constraints. For your largest workloads: what actually binds, residency, latency, elasticity, or cost?
  • 4Diary the two clocks. Any Cloud at Customer: the consumption expiry and the hardware term, both into the calendar.
  • 5Map the spectrum. Your estate placed across owned, Cloud at Customer, cloud service, dedicated region, and public.
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