IBM Db2 · licensing and audit
IBM Db2 licensing and audit defense.
Db2 editions are licensed on processor value units, and the metric is where most audit findings begin. We recalculate the PVU position, defend the sub-capacity claim, and challenge the bundling assumptions IBM uses to widen scope. Independent, not affiliated with IBM.
How Db2 is licensed.
Most Db2 editions meter on processor value units, with sub-capacity available only under strict conditions.
Metric
Processor value units
PVU is a core based metric: the PVU rating for your processor type, for example roughly 70 PVU on a common Intel core, multiplied by the cores allocated to Db2. Cost ties directly to the hardware Db2 can run on.
- Full capacity counts every physical core on the host
- Sub-capacity counts only the virtual cores running Db2
- Some Db2 packs and connectors carry their own entitlement limits
Sub-capacity
ILMT is the condition
To license virtual cores instead of the whole host, ILMT (or an approved tool) must be deployed within 90 days of first eligible use, run continuously, and produce quarterly reports kept for two years. Miss any one and IBM defaults the line to full capacity.
- WebSphere style math applies: 4 of 32 cores is a fraction of the full-capacity number
- Broken or missing agents void the claim for that period
- The lookback can reach back two to five years
Common Db2 audit traps.
01
Bundled Db2 used beyond scope
The Db2 entitlement bundled with Cognos or another product is restricted to that product. Using it as a general database is a frequent finding.
02
Sub-capacity defaulted to full
Thin or misconfigured ILMT data lets IBM charge every core on the host rather than the cores Db2 actually uses.
03
Editions counted up
Advanced features or a higher edition assumed where a lower edition is deployed inflates the PVU position.
04
Idle cores on Power
On LPAR and Power, allocated cores count even when idle, so a generous partition raises the count.
05
Non production not separated
Cold standby and certain non production copies have specific rules that are easy to misapply against you.
06
Term and BYOL mismatch
Term licenses and bring your own license deployments on cloud carry posture rules that audits probe.
How we defend Db2.
01
Contain
Scope the data request so only the Db2 evidence that helps your position leaves the network.
02
Reconcile
Recalculate Db2 PVU against entitlements and Passport Advantage records, sub-capacity where it holds.
03
Challenge
Dispute bundling reach, wrong PVU values and denied sub-capacity item by item.
04
Settle
Reduce the number and fold reinstatement and forward terms into the settlement.
Related services.
Read next.
Do not face the IBM audit alone.
$250M+ in exposure defended. 500+ engagements. We mobilize within 48 hours of your audit notice. Independent and buyer side, every time.
Get audit help now →The IBM Audit Brief
Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.
IBM Audit
Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.
Independent. Not affiliated with IBM Corporation.Buyer Side · Est. 2019