PVU counts processor power. VPC counts virtual cores. UVU counts user volumes. The wrong metric on the wrong workload prints a five to seven figure swing across a three year audit cycle.
IBM Db2 prices under three distinct metrics. PVU counts processor power. VPC counts virtual cores. UVU counts user volumes for the warehouse editions. The metric choice sets the license footprint for the term.
The buyer side discipline is to map each Db2 deployment to the right metric, then apply the sub capacity rules and the ILMT requirements correctly. The wrong order is to accept the IBM proposed metric, then reverse engineer the math.
Read this article alongside the IBM knowledge hub, the IBM advisory practice, the IBM audit defense, the IBM audit defense playbook, the IBM license audit defense service, and the Vendor Shield subscription.
PVU stands for Processor Value Unit. It rates the relative power of a processor core. IBM publishes a PVU table that assigns a PVU value to each supported processor family.
| Processor family | PVU per core | Typical use | Audit note |
|---|---|---|---|
| Intel Xeon and AMD EPYC | 70 | x86 server deployments | Most common Db2 footprint |
| IBM Power9 and Power10 | 120 | Power LPAR deployments | Higher PVU per core |
| IBM Z mainframe | 120 | z/OS workloads | MSU or MIPS based for Z |
| ARM neoverse | 70 | Cloud native deployments | Cloud provider issued |
The database team deploys Db2 on a sixteen core x86 host without configuring ILMT correctly. The sub capacity report fails to produce. The audit team applies full capacity at seventy PVU per core. The license requirement balloons against the entitled count.
VPC stands for Virtual Processor Core. It counts the number of virtual cores the workload consumes. The metric suits virtualized and cloud deployments where the PVU table does not map cleanly.
A migration team converts from PVU to VPC without modeling the credit pool inside the cloud pak. The Db2 estate consumes more cloud pak credits than the converted PVU entitlement provided. The renewal lands at a higher cloud pak commitment than the original perpetual bill.
UVU stands for User Value Unit. The metric applies to Db2 Warehouse Advanced Edition and certain analytics SKUs. Authorized user pricing also applies under specific entitlements.
An analytics team grants Db2 access to a broad business user community through a reporting tool. The reporting tool aggregates the queries through a service account. The audit team reads the underlying business user list and bills the authorized user count against every unique consumer of the warehouse.
Sub capacity licensing reduces the PVU count from the full physical capacity of the server to the actual virtual capacity allocated to the Db2 workload. The discipline depends on ILMT.
| Requirement | Detail | Audit consequence | Buyer note |
|---|---|---|---|
| ILMT installed | Active on every server running PVU | Missing ILMT defaults to full capacity | Non negotiable |
| ILMT reporting | Quarterly reports archived for two years | Missing reports trigger reassessment | Calendar quarterly |
| VM partition fix | Hard partition where possible | Soft partition can be challenged | Document the architecture |
| Virtualization technology | Approved hypervisor list only | Unapproved hypervisor loses sub capacity | Check the IBM list annually |
Missing ILMT reports turn a sub capacity entitlement into a full capacity exposure. A sixteen core host with a four core Db2 LPAR can balloon from 280 PVU to 1,120 PVU on a missing report. The license multiplier follows the same curve.
The buyer side fix is to calendar the ILMT report generation quarterly and to archive every output for at least two years. The archive is the audit defense file.
IBM Cloud Pak for Data wraps Db2 inside a credit pool. The perpetual Db2 estate can convert into the cloud pak at a defined ratio. The conversion can collapse the support stream and the audit exposure.
The Db2 metric choice sets the audit exposure for the term. Walk into the IBM conversation with the PVU table, the ILMT archive, and the cloud pak credit model already in hand. The price drops twenty to forty percent when the buyer arrives with a complete metric by metric picture.
The seven step checklist below is the buyer side starting position for any Db2 licensing review.
PVU rates processor power across processor families with values from seventy to one hundred twenty per core. VPC counts virtual cores allocated to the workload. PVU sub capacity requires ILMT installed and reporting. VPC counting is more common in cloud and containerized deployments under the cloud pak model. The metric choice sets the entitlement count for the term.
Yes. IBM sub capacity licensing for Db2 PVU requires the IBM License Metric Tool installed on every server that runs Db2 under sub capacity. Quarterly reports must be generated and archived for at least two years. Missing ILMT or missing reports defaults the license requirement to full capacity at the processor PVU rate.
IBM Cloud Pak for Data wraps Db2 inside a credit pool. The perpetual Db2 estate converts to cloud pak credits at a published ratio. The cloud pak includes Db2, DataStage, Watson Knowledge Catalog, and other Cloud Pak for Data components. The credit pool sizing matters most. Under sized pools trigger overage at the next renewal.
UVU stands for User Value Unit. Db2 Warehouse Advanced Edition and certain analytics SKUs price under UVU. The user count covers every unique consumer of the warehouse. External applications that aggregate queries through a service account still create indirect user exposure under the metric. The audit team reads the underlying business user list.
Missing or incomplete ILMT reports, unauthorized virtualization technology, soft partitioning that does not meet the IBM sub capacity rules, growth in user counts under UVU, and cloud pak credit pool under sizing. The audit team can request ILMT archive history. Missing reports default the license to full capacity at the processor PVU rate.
Redress runs IBM Db2 engagements inside Vendor Shield, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. The work covers metric mapping, ILMT discipline, sub capacity audit defense, cloud pak conversion modeling, and renewal lever negotiation. Always buyer side, never IBM paid.
Redress runs IBM Db2 engagements inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. The IBM commercial leadership sits with the practice lead.
Read the related benchmarking framework, about us, locations, and contact pages.
A buyer side reference on IBM commercial leverage, the Db2 metric map, the ILMT discipline, the cloud pak conversion model, and the renewal levers. Built from hundreds of IBM engagements.
Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying IBM estates. No IBM influence. No sales kickback.
Open the white paper in your browser. Corporate email only.
Open the Paper →The Db2 metric choice sets the audit exposure for the term. Walk into the IBM conversation with the PVU table, the ILMT archive, and the cloud pak credit model already in hand. The price drops twenty to forty percent when the buyer arrives with a complete metric by metric picture.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
Db2 metric mapping, ILMT discipline, sub capacity audit defense, cloud pak conversion math, and the wider IBM commercial leverage signals across every renewal we run.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
