Oracle EBS Processor Licensing Explained

The Processor Metric in Oracle EBS Licensing

The Processor metric is Oracle's infrastructure-based licensing unit for E-Business Suite. Rather than counting users, a Processor license is tied to the physical hardware running the EBS application and database software. One Processor license is required for each processor in a server, with the exact count determined by applying the Core Factor Table to the actual number of cores in that processor.

For Oracle EBS, Processor licensing typically applies to the database tier (Oracle Database Enterprise Edition or Standard Edition) and optionally to the application server tier. Most enterprise EBS deployments use Processor licensing for the database and either Processor or Named User Plus licensing for the application layer, depending on user volume and contractual terms.

Oracle defines a Processor as "all processors where the Oracle programs are installed and/or running." This definition has significant implications for virtualized and cloud environments where EBS may technically run on more physical capacity than is actively assigned to it.

How the Core Factor Table Works

The Core Factor Table is Oracle's mechanism for normalizing license costs across different processor architectures. Because a modern 32-core Intel chip and an older SPARC chip have very different compute characteristics, Oracle assigns each chip type a "core factor"—a multiplier that converts physical cores into Oracle Processor license equivalents.

The formula is straightforward: Total Cores x Core Factor = Processor Licenses. The core factor varies by chip manufacturer, architecture, and model. Intel and AMD x86 processors carry a core factor of 0.5, meaning every two physical cores equals one Processor license. IBM POWER processors carry factors ranging from 0.5 to 1.0 depending on generation. Oracle's own SPARC processors often carry a factor of 0.25 to 0.5.

The table is maintained by Oracle and can be updated. Oracle has used updates to the Core Factor Table to retroactively increase license obligations—a practice that has created disputes with customers who planned infrastructure investments based on earlier factor values. Any organization sizing its EBS infrastructure should obtain the current published Core Factor Table and verify its hardware entries before finalizing purchase decisions.

Processor Type	Core Factor	Example: 32 Cores	Processor Licenses
Intel x86 / AMD x86	0.5	32 cores	16
IBM POWER8/9	1.0	32 cores	32
IBM POWER10	0.5	32 cores	16
Oracle SPARC T-Series	0.25	32 cores	8
Oracle SPARC M-Series	0.5	32 cores	16

Virtualization and the Full Partition Rule

Virtualization dramatically complicates EBS Processor licensing. Oracle's default position is that unless you use Oracle VM Server for x86 (OVM) or Oracle's own virtualization technology, you must license all physical cores on the host server—not just the cores assigned to the EBS virtual machine.

This rule, often called the full partition rule, means that running EBS in a VMware vSphere cluster requires you to license every physical core in the cluster, not just the cores allocated to the EBS guest. For a 10-node VMware cluster with 32 cores per node, that is 320 physical cores x 0.5 core factor = 160 Processor licenses, even if EBS runs on a single VM assigned 8 virtual CPUs.

Oracle's position on VMware has been particularly contentious. In 2022, Oracle published guidance reaffirming that VMware does not constitute a "hard partition" under Oracle's virtualization policy and that customers must license all physical cores on VMware hosts. This position survives even after Broadcom's acquisition of VMware. Organizations running EBS on VMware should treat this as an active compliance risk requiring immediate quantification. Our Oracle EBS Licensing Guide covers virtualization policy in full detail.

Oracle Hard Partitioning: The Only Safe Virtualization Path

Oracle recognizes only a limited set of hard partitioning technologies that allow customers to license fewer than all physical cores on a server. These include Oracle VM Server for x86, Oracle Solaris Zones (in certain configurations), IBM's LPAR with specific micropartitioning settings, and a handful of hardware-based partitioning solutions from Sun and HP.

Critically, VMware, Hyper-V, KVM, and most public cloud virtualization layers are not Oracle hard partitions. AWS, Azure, and Google Cloud all use shared physical infrastructure, and Oracle treats them as requiring full physical core licensing unless you are using Oracle's own cloud (OCI) or a licensed Dedicated Host configuration. The specific rules differ by cloud provider and are documented in Oracle's cloud licensing policies.

Organizations that have deployed EBS in AWS or Azure under the assumption that they only need to license the vCPUs assigned to their instances are carrying significant unquantified compliance risk. Oracle's LMS auditors specifically probe for cloud deployments and have pursued substantial claims against customers who relied on virtual CPU counts rather than physical host counts.

Processor Count Calculation for Multi-Tier EBS Deployments

A standard Oracle EBS deployment involves multiple tiers: the application tier (running Oracle WebLogic Server and EBS concurrent managers), the database tier (running Oracle Database), and optionally a web tier. Oracle licensing rules require Processor licenses for each tier independently unless the license agreement grants rights to use additional technology on the application tier by virtue of the EBS application license.

The application tier requires licensing for Oracle Fusion Middleware and WebLogic Server components embedded in EBS. In many Oracle license agreements, this is bundled within the EBS application license, but the terms vary significantly by contract vintage and negotiated scope. Organizations operating on older EBS agreements should explicitly verify whether their application tier middleware is covered or requires separate Processor licensing.

For the database tier, Oracle Database Enterprise Edition is the typical requirement for EBS, and any Database Options deployed—Partitioning, Diagnostics Pack, Tuning Pack, Advanced Security, Real Application Clusters—require separate Processor licenses. Oracle's USMM tool identifies which Database Options are active, and organizations frequently find Options running by default that were never intentionally licensed.

Processor Licensing vs. Named User Plus: Which Is Better for EBS?

The choice between Processor and Named User Plus licensing for Oracle EBS depends on the relationship between server size and user population. Processor licensing is effectively a per-unit-of-infrastructure charge, while Named User Plus is a per-person charge with a Processor-based minimum floor.

For organizations with large user populations relative to server size—typically organizations with more than 100 users per Processor license—Processor licensing is often more cost-effective. For smaller organizations or those with lightly staffed EBS deployments, Named User Plus may offer a lower total cost, but only if the user count genuinely falls below the Processor minimum threshold.

Our Oracle license optimization service performs this analysis as part of every EBS engagement, identifying whether your current metric mix is optimal and what restructuring opportunities exist at renewal. See also our Oracle EBS licensing white papers for detailed cost comparison frameworks.

Processor Licensing Audits: What Oracle Checks

When Oracle's LMS team audits an EBS Processor count, they collect hardware inventory data including server specifications, virtual machine configurations, and cloud instance types. They cross-reference this data against Oracle's Core Factor Table and apply the appropriate factors to arrive at a Processor license count.

Common audit findings for EBS Processor licensing include organizations that have added servers, expanded virtual machine clusters, or migrated to larger cloud instances without corresponding license amendments. Oracle considers any processor running EBS software at any point during the audit period to be a licensable event—not just current deployments.

Organizations that have undergone infrastructure migrations, cloud transitions, or disaster recovery deployments should carefully document what hardware has run EBS software and when. Our Oracle Audit Defense Guide covers the documentation requirements and negotiating strategy for Processor-based EBS audit claims. Contact our team for a confidential pre-audit review via our audit defense service.

Oracle Licensing Experts is an independent advisory firm. Not affiliated with Oracle Corporation. Oracle, Java, and Oracle E-Business Suite are registered trademarks of Oracle Corporation.