Licensing glossary
What is an Oracle Processor license and core factor?
An Oracle Processor license counts the physical cores where the program is installed or running, multiplied by the core factor for that processor, then rounded up to a whole number.
How it works
For Enterprise Edition and its options, count every physical core on every processor where the programs are installed and/or running, multiply by the factor Oracle's Core Factor Table gives that processor model, and round up once per server. Hyper-threading does not change the count: a 16-core processor with 32 threads is 16 cores.
The factors run from 0.25 to 1.0. Current Intel Xeon and AMD EPYC servers are 0.5, IBM POWER is 1.0, and a processor the table does not list is 1.0. Standard Edition 2 is licensed per socket instead, and on AWS and Azure Oracle's cloud policy replaces the table altogether.
Worked example
Rounding happens after the multiplication, per server:
- Xeon server, 6 cores
- 6 × 0.5 = 3 licenses
- Xeon server, 7 cores
- 7 × 0.5 = 3.5, so 4 licenses
- POWER9 partition, 8 cores
- 8 × 1.0 = 8 licenses
- 32-license database with Partitioning and Diagnostics Pack
- 96 licenses across three products
Each option and pack in use is licensed to the same processor count as the database it runs in.
What to watch
- Counting the VM's vCPUs. The factor applies to the physical cores of the host, and under Oracle's partitioning policy usually to every host in the cluster.
- Applying 0.5 to a processor that is 1.0. IBM POWER is the usual case.
- Rounding before multiplying, or using the cloud rule on premises. They are different documents with different arithmetic.
- Recording core counts without CPU models. Two 32-core servers can differ by 32 licenses if one is Xeon and the other POWER.