What does right sizing an Oracle estate mean?
Right sizing an Oracle estate means matching the capacity you license to the capacity you actually use, by retiring idle databases and shrinking oversized hosts before the licence count is set. Estates accrete over years: a project spins up a database, the project ends, the database lingers, and it keeps consuming licences and support. Because the Processor metric follows physical cores multiplied by the core factor, every core you license on a host you do not need is paid for twice, once in the licence and again in the roughly 22 percent annual support that escalates each year. Right sizing finds that waste and removes it first, which is why it belongs at the front of any database licensing exercise. The full method sits in the Oracle Database Licensing Guide.
Can you reduce Oracle licences by reducing cores?
Yes, you can reduce Oracle licences by reducing cores, because the Processor count is physical cores times the core factor, so fewer licensable cores means fewer licences. Consolidating several lightly used databases onto a smaller, properly counted host, or capping cores on an oversized server, lowers the count directly. The catch is that the reduction has to be done in a way Oracle recognises, which means the licensable boundary has to be real and documented, not just a claim that the workload is small. Soft caps that Oracle does not accept will not lower the count, so the work is to make a hardware or partitioning change that genuinely reduces licensable cores and to keep the evidence that proves it.
Before licensing a host, ask whether its cores match its workload. Consolidate idle databases, cap or remove cores Oracle will recognise, and document the change. Every core removed is a licence and a recurring support fee you stop paying.
How do you find the idle databases?
You find idle databases by reviewing connection activity, feature usage, and ownership across the estate, looking for instances that nobody connects to and no application depends on. The candidates are familiar: an old reporting copy, a migration source left running after cutover, a development database for a project that shipped a year ago. Each one is verified with the owning team before anything is switched off, because the cost of decommissioning a live system is far higher than the saving. Once an idle database is confirmed and retired, its licences free up for reuse elsewhere, which can remove the need to buy at all. For the numbers behind the per database decision, see the database licensing worked example, and to pick the cheaper metric on what remains, see processor versus Named User Plus.
Does dropping Oracle support save money safely?
Dropping Oracle support saves money only when you understand the repricing risk, because terminating support on some licences can trigger Oracle to reprice the support on the ones you keep under matching service level rules. The rule means you cannot always cherry pick the licences to drop without Oracle recalculating the remainder at a higher rate, which can erase the saving. Right sizing comes first because it reduces the licences you hold in a clean way, and any support change is then planned with the repricing mechanics understood rather than discovered after the fact. This is contract dependent, so the exact constraint depends on your agreement and should be read before any termination decision.
| Lever | What it cuts | Watch for |
|---|---|---|
| Retire idle databases | Licences and support | Confirm with owning team first |
| Consolidate onto smaller hosts | Processor count | Boundary must be Oracle recognised |
| Cap or remove cores | Processor count | Soft caps may not count |
| Plan support changes | Annual support fee | Matching service level repricing |
What is the next step?
The next step is to inventory the estate, flag the idle and oversized hosts, and model the licence and support saving before you buy or renew anything. Right sizing routinely takes a meaningful slice off a Processor count, and because support follows the count, the saving repeats every year. Get a quote to have us inventory your databases, confirm what can be retired or consolidated, and model the licence and support reduction with the repricing risk mapped, so the savings are real and defensible.
Get a quote to inventory the estate, identify what can be retired or consolidated, and model the licence and support saving. Start at the contact page, or read the full Oracle Database Licensing Guide.