Skip to content
Oracle Licensing Playbook

Know which Oracle options are actually running — measured across your estate, not declared on an LMS script

Oracle’s most expensive surprises come from options and packs that switch on quietly, processor counting that turns on the core-factor table, and virtualization rules that count more cores than you run. This is the buyer-side playbook for reaching your own defensible number — before a renewal or review.

Oracle licensing is complex and metric-dependent, and small counting errors compound into six-figure true-ups. The good news: your position is knowable. What each database runs, which options are in use, and how the core factor applies to your hardware are all measurable today — RenewalIntel makes that visible before a renewal or review does the math for you.

Where exposure hides

Three places Oracle exposure builds up unseen

Options & packs you didn’t license

Diagnostics Pack, Tuning Pack, Partitioning and the rest bill separately — and a default-on feature or a single DBA action can switch one on without anyone noticing. RenewalIntel surfaces which options are actually in use, traced to the database, so you can license what you need or turn off what you don’t — before a review, not after.

Processor counting and the core factor

Whether a database is licensed by Processor or Named User Plus, your number turns on the Oracle core-factor table and the NUP minimums. RenewalIntel applies the current core factors to your real core inventory per database and converts NUP to processor-equivalents — the deterministic math, done against your estate.

Virtualization counts more than you run

On VMware and other soft-partitioned hosts, Oracle’s policy counts cores beyond where the database actually runs. RenewalIntel flags where Oracle is installed on virtualized hosts so the exposure is visible — whether Oracle’s partitioning policy entitles them to count the whole host is a contract question for you and your advisor.

Why a measurement, not a one-time review

Continuous evidence beats a point-in-time snapshot

An Oracle licensing advisor brings deep negotiation and contract expertise — and you may well want one at the table. But a review is a snapshot: accurate the day it’s taken, blind to the management pack that switches on next quarter or the option a patch enables by default. RenewalIntel watches what your databases actually run, every connector cycle, and traces every billable option back to the database and feature that triggered it. Hand that to your advisor, your CFO, or Oracle — and the conversation starts from evidence, not a self-declared worksheet.

How it works

From deployment inventory to a defensible position

1

Bring in your data

Pull your Oracle deployment inventory via the read-only on-prem agent, and your entitlements from the contracts you hold. Nothing reaches into your databases.

2

Reconcile per database

RenewalIntel applies the core-factor table to your real cores, converts NUP to processor-equivalents, and compares what each option/pack has in use against what you’re licensed for.

3

Get the verdict + evidence

A clear position per product, the gap estimated at Oracle list pricing, and prioritized recommendations — every number traced to the database and feature that drove it.

Know your Oracle position before the review

Reconcile your real Oracle deployment against your entitlements — options in use, core factor applied, in minutes. No credit card required.

Oracle, Java, and related product names are trademarks of Oracle Corporation and/or its affiliates. RenewalIntel is not affiliated with, sponsored by, or endorsed by Oracle. Vendor names identify reconciliation coverage only. RenewalIntel is software for measuring your own licensing position; it is not legal, audit, or licensing-advisory services.