Oracle options and management packs are licensed separately from the database and counted by processor on the servers where they run. Only the ones named in your ULA carry the unlimited right, so the task at certification is to capture every in scope pack you deployed without claiming any you did not.
Counting the database itself is only part of a certification. Sitting on top of the database is a layer of separately licensed options and management packs, and they behave differently from the core product. They are easy to miss when they are in scope, and easy to trip over when they are not. Handling this layer correctly is what separates a complete count from one that either leaves value behind or invites a compliance question.
Yes. Database options such as Partitioning, Advanced Security, Advanced Compression, and Real Application Clusters are licensed separately from the database and counted by processor on the servers where each one runs. The same processor counting logic applies, meaning you apply the core factor to the cores in scope for each option, server by server. Crucially, only the options listed in your ULA carry the unlimited right. An option you ran that is not in your agreement was never covered by the ULA and does not certify into a perpetual entitlement.
This is why reading the product list in the agreement comes first. The list defines which options you may count without limit. Everything inside it is yours to capture in full at exit. Everything outside it is ordinary licensing and has to be treated as such.
Management packs, such as the Diagnostics Pack and the Tuning Pack, carry a particular subtlety. They can register as used through features enabled in the database, sometimes without anyone deliberately adopting them. A feature switched on by a default setting or by a routine administrative action can light up pack usage in Oracle's own views. At certification you count the packs that are both within your ULA scope and genuinely deployed, and you support each with evidence of where it runs.
The discipline cuts both ways. A pack in your scope that you genuinely use is value to capture. A pack outside your scope that has quietly registered usage is a compliance question to understand and address before it surfaces in the years after certification. Either way, you want to know the real picture before you declare anything.
For options and packs inside your ULA scope, count completely, because they convert to permanent entitlement at no extra support cost. For options and packs outside your scope, identify them and decide deliberately whether to license, decommission, or disable before exit. The principle is the same as the rest of the count: know the truth, then act on it with evidence behind every line.
Options frequently slip through a count because the team measures the database and stops. Partitioning running across a large estate, Real Application Clusters on the production tier, Advanced Security protecting sensitive systems, all of these are in scope under many ULAs and all are routinely under counted. Management packs slip through in the opposite direction, registering usage nobody intended. A complete count looks at both, server by server, and reconciles what it finds to the product list in the agreement.
Start from a discovery that reports option and pack usage per database, not just the database edition. Map each option and pack you find to the product list in your ULA. For everything in scope, count it by processor using the same core factors as the database and capture the evidence. For anything out of scope that shows usage, investigate how the usage arose and decide on a deliberate remediation before the window closes. The result is a count that captures the full in scope layer while carrying no surprises into the post certification years.
This layer sits on top of the core count covered in counting Oracle deployments for certification. Whatever you count, you have to be able to prove, which is the subject of evidence that supports every number. For the full exit picture, see our Oracle ULA certification guide.
Yes. Options such as Partitioning, Advanced Security, and Real Application Clusters are licensed separately from the database and counted by processor on the servers where they run. Only the options listed in your ULA carry the unlimited right.
Management packs can register as used through features enabled in the database, even without deliberate adoption. At certification you count packs that are in your ULA scope and genuinely deployed, supported by evidence of where each one runs.
We map every option and pack to your agreement, count what is in scope, and resolve what is not before you certify.