Practice i · Database
Oracle Database Licensing
Independent buyer side advisory for Oracle Database Enterprise Edition, Standard Edition 2, options, and management packs.
Independent buyer side advisory for Oracle Database Enterprise Edition, Standard Edition 2, options, and management packs.
Oracle database licensing is governed by two metrics, Processor and Named User Plus, multiplied by a core factor table and complicated by options and management packs that bill separately. A buyer side review prices the estate against the contract rather than the install, and typically removes most of an option pack claim.
Oracle Database is the highest value line on most enterprise estates and the most exposed. Enterprise Edition is licensed per Processor, where the count is physical cores multiplied by the core factor for the chip, or per Named User Plus subject to per processor minimums. Standard Edition 2 uses a socket based metric with its own ceiling on cores. The two editions are not interchangeable, and a Standard Edition deployment that crosses the threshold becomes an Enterprise Edition liability overnight.
The exposure rarely comes from the database itself. It comes from options and management packs. Partitioning, Advanced Compression, Advanced Security, Real Application Clusters, Diagnostics Pack, Tuning Pack, and a dozen others bill on top of the Enterprise Edition licence and at full processor count. Oracle's measurement scripts capture every option that has ever been touched, including features enabled once by a previous administrator and never used in production. The default LMS finding assumes everything seen is everything owed.
Virtualisation multiplies the problem. Oracle's partitioning policy treats VMware and most hypervisors as soft partitioning, which under Oracle's reading licenses every physical core in the cluster the database could theoretically run on, not the cores it actually uses. A single database on a large vSphere cluster can generate a claim for hundreds of cores. The policy is not contractual, and that distinction is the whole of the argument.
We unwind these claims by measuring what was actually enabled, by whom, and under what authority, then mapping each finding to the contractual definition that governs it. Three quarters of a typical option pack claim dissolves on documentary grounds before a single dollar is conceded.
Validation of processor counts against the current core factor table, correction of chip misclassification, and rebalancing of Enterprise Edition against Standard Edition 2 where the workload allows.
A line by line audit of which database options and management packs are genuinely in use, who enabled them, and whether usage is contractually licensable as found.
User population counting against per processor minimums, with a defended methodology for multiplexed and batch access.
Assessment of VMware, Oracle VM, and LPAR topologies against Oracle's partitioning policy, and remediation of soft partitioning exposure.
A single reconciled view of entitlement versus deployment across every database instance, environment, and disaster recovery copy.
Review of the support contract, repricing exercises, and removal of shelfware before the next renewal locks it in.
We open the channel with Oracle on your terms, fix the scope of the conversation, lock the calendar, and ensure no measurement data leaves the perimeter without buyer side review.
An independent measurement against the same ruleset Oracle applies, performed earlier and with cleaner data. Every finding is categorised by exposure tier and tied to the contract clause that governs it.
Findings are documented and argued line by line. Concessions are priced. We have sat on Oracle's side of these tables and know which positions hold and which dissolve.
The settlement is converted into forward commercial value rather than backward payment, with renewal protections, audit cure provisions, and portability written into the result.
Database engagements are scoped to the size and risk of the estate. A focused option pack defence or core factor review fits a fixed fee. A full estate baseline with ongoing renewal management suits a retainer. Where the work is triggered by an active claim, a gain share arrangement aligns our fee with the reduction we secure.
The right structure depends on the engagement. Read our engagement model overview to see when a fixed fee, a retainer, or a gain share arrangement fits, then request a consultation to scope your estate.
The core factor is a multiplier Oracle assigns to each processor type. To count processor licences for Enterprise Edition you multiply the number of physical cores by the core factor for that chip. Most current x86 cores carry a 0.5 factor, so two cores equal one licence, but the table changes and misclassification is a frequent and expensive error.
Enterprise Edition is licensed by Processor or by Named User Plus. The Processor metric counts cores times the core factor. Named User Plus counts the individuals and devices accessing the database, subject to a minimum number of users per processor. Options and management packs are licensed separately and on the same metric as the underlying database.
Oracle's partitioning policy classifies VMware as soft partitioning and asserts that every physical core the database could run on must be licensed. That policy is a document, not a contract term. Whether it binds you depends on your agreement and your architecture, and it is the central question in most virtualisation claims.
Options such as Partitioning, Advanced Compression, Advanced Security, and Real Application Clusters add capability to Enterprise Edition and bill on top of it at full processor count. Management packs such as Diagnostics Pack and Tuning Pack are licensed the same way. Enabling one without an entitlement is the most common source of audit exposure.
Named User Plus is a per user metric that counts every individual and non human operated device authorised to access the database. It is subject to a minimum number of users per processor, so on large servers the processor metric is often cheaper. Multiplexing through a middle tier does not reduce the count under Oracle's definition.
Yes. Standard Edition 2 is restricted by socket and by a maximum number of CPU threads. A deployment that grows past those limits, or that uses a feature only available in Enterprise Edition, converts into an Enterprise Edition obligation that Oracle will price at the higher metric.
Before a renewal, before a virtualisation project, and immediately on any LMS or GLAS contact. The earlier the measurement, the more options remain open and the lower the eventual settlement. Engaging after a claim lands narrows the room to negotiate.
WebLogic, SOA Suite, and the option packs that ride the same processor metric as the database.
View the practice →End to end response when an LMS or GLAS database finding lands, from notification to settlement.
View the practice →When database growth justifies an unlimited agreement, or when certification is the cheaper exit.
View the practice →A buyer side measurement of your Oracle Database position, performed earlier and with cleaner data, is the single highest return action available before a renewal or an audit.