For a broader view of IBM licensing across all products, see our IBM Licensing Knowledge Hub.
1. IBM DB2 Licensing Models Explained
PVU, Authorised User, and Concurrent User metrics compared
IBM offers multiple licensing models for DB2, tailored to fit various enterprise scenarios. The two primary models are Processor Value Unit (PVU) and Authorised User licensing.
| Licence Metric | How It Works | Best Suited For | Key Requirement |
|---|---|---|---|
| Processor Value Unit (PVU) | Licences based on server processing power. IBM assigns a PVU value to each CPU core (e.g. a modern x86 core = 70 PVU). You purchase enough PVUs to cover all cores where DB2 runs. Allows unlimited users. | Large-scale deployments, web-facing applications, unpredictable or high user counts | Sub-capacity requires ILMT deployment within 90 days |
| Authorised User | Licences tied to named individuals who access DB2. Each user needs a licence for each DB2 instance they use. Minimum purchase quantities apply. | Smaller teams, internal applications with a limited, identifiable user base | Min 5 users/server (Workgroup) or 25 users per 100 PVUs (Enterprise). Non-transferable between individuals. |
| Concurrent User (DB2 Connect) | Sold in bundles of 25 users for connecting distributed applications to mainframe or iSeries DB2. Counts simultaneous connections rather than named users. | Mainframe DB2 access from distributed applications | Sold in fixed 25-user packs. Cannot purchase fractional bundles. |
💡 PVU Is the Default for Most Enterprise Deployments
In practice, PVU licensing is the most common choice for enterprise DB2 environments. It provides unlimited user access on licensed servers and supports sub-capacity licensing in virtualised environments. Authorised User licensing only makes economic sense when the user population is small, stable, and well-defined, typically fewer than 30-40 users per server. Beyond that threshold, PVU almost always wins on cost.
For a deeper dive into PVU mechanics, read our IBM PVU Licensing: practical guide for ITAM professionals.
2. Choosing the Right DB2 Edition
Workgroup, Enterprise, Advanced, and Cloud editions compared
IBM DB2 comes in a range of editions, each tailored to different use cases and organisational sizes. Picking the correct edition is as important as the licensing model. Choosing too high an edition wastes budget, while choosing too low can breach licence terms if you exceed its limits.
| Edition | Resource Limits | Licence Metrics | Key Features | Best Suited For |
|---|---|---|---|---|
| Workgroup Server Edition | Max 16 cores, 128 GB RAM | PVU or Authorised User (min 5 users/server) | Core DB2 for transactional workloads. Cost-effective for smaller deployments. | Department-level, mid-sized databases with modest resource needs |
| Enterprise Server Edition | No limits on cores or memory | PVU or Authorised User (min 25 users per 100 PVUs) | All Workgroup features plus unlimited scalability, advanced performance, high availability | Large-scale, mission-critical production systems |
| Advanced Workgroup Edition | Max 16 cores, 128 GB RAM | PVU, User, or per-TB | Workgroup features plus compression, partitioning, BLU Acceleration (in-memory analytics) | Mid-sized analytics or warehousing requiring advanced features |
| Advanced Enterprise Edition | No limits | PVU, User, or per-TB | Full DB2 functionality including analytics, warehousing, partitioning, compression | Enterprise-scale data warehousing and complex analytics |
| DB2 Direct / Cloud Editions | Varies | Subscription (monthly vCPU or cloud credits) | Cloud-native or containerised DB2 deployments | Cloud-first strategies, Kubernetes/OpenShift environments |
Need Help Determining the Optimal DB2 Edition?
Our IBM advisors assess your environment, usage patterns, and growth projections to recommend the right edition and licensing model.
IBM Licensing Assessment →3. Key Cost Drivers in IBM DB2 Licensing
Six factors that determine your total cost of ownership
| Cost Driver | Impact | Mitigation Strategy |
|---|---|---|
| CPU Cores / PVU Count | More cores and higher PVU ratings per core = more PVU licences required. Hardware upgrades directly increase licence cost. | Choose efficient processors. Limit cores allocated to DB2 via virtualisation. Use sub-capacity licensing. |
| User Count | Every authorised user adds cost. IBM enforces minimum licence bundles (5 or 25 users). Large user populations make per-user licensing extremely expensive. | Switch to PVU when user count exceeds ~30-40 per server. Remove inactive users regularly. |
| Virtualisation (Sub-Capacity) | Can dramatically reduce cost: licence only the VM’s allocated cores instead of full physical capacity. But requires ILMT deployment and compliance. | Deploy ILMT within 90 days. Generate quarterly reports. Use only IBM-approved hypervisors. |
| DB2 Edition and Features | Higher editions and add-on features (compression, partitioning, BLU) carry higher licence fees. Unused advanced features = wasted spend. | Match edition to actual requirements. Do not pay for Advanced features you do not use. |
| Annual Support (~20%) | IBM annual maintenance is typically ~20% of licence value. Over 5 years, support costs equal the original licence investment. | Negotiate multi-year commitments. Consider ELA bundling for volume discounts. Evaluate third-party support for stable environments. |
| Non-Production Environments | Dev, test, DR all require licences unless specific contractual exceptions exist. Often overlooked in budgets. | Use IBM’s free Developer Edition for non-production. Minimise core allocations on test VMs. |
💡 Always Model Multiple Scenarios Before Committing
Before purchasing DB2 licences, calculate costs under both PVU and Authorised User models. Factor in projected user growth, planned hardware changes, and the impact of virtualisation. Include 5-year support costs in your total cost of ownership (TCO) calculation. Support alone can exceed the original licence investment over a typical enterprise lifecycle.
📄 White Paper
10 Costly IBM Licensing Mistakes: A Practical Guide for CIOs
Common licensing errors across DB2, WebSphere, MQ, and Cognos, including sub-capacity failures, edition misuse, and ELA traps that cost enterprises millions.
Download White Paper →For IBM bundling strategies that affect DB2 pricing, see our guide on IBM bundling and licensing practices explained.
4. Sub-Capacity Licensing and ILMT
The single biggest cost-saving mechanism in IBM DB2 licensing
Sub-capacity licensing is one of the most significant cost-saving mechanisms available for IBM DB2, but it comes with strict requirements. Without meeting these requirements, IBM defaults to full-capacity licensing, which can multiply your costs by 2-3x or more.
| Licensing Mode | How It Works | Requirements | Cost Impact |
|---|---|---|---|
| Full Capacity | Licence all physical processor cores on the server where DB2 runs, regardless of actual usage | None. This is the default. | Expensive. A 16-core server = 16 x 70 = 1,120 PVUs even if DB2 uses only 4 cores |
| Sub-Capacity (Virtualisation) | Licence only the virtual cores allocated to DB2 in a VM or partition | ILMT deployed within 90 days. Quarterly reports archived. IBM-approved hypervisor only. | Major savings. 4 vCores on a 16-core server = 4 x 70 = 280 PVUs (75% reduction) |
📊 Cost Impact Example: Sub-Capacity vs Full Capacity
A global manufacturer runs IBM DB2 Enterprise on a VMware cluster. The VM uses 8 virtual cores on a physical host with 32 cores (x86, 70 PVU/core).
With ILMT (sub-capacity): 8 cores x 70 PVU = 560 PVUs required
Without ILMT (full capacity): 32 cores x 70 PVU = 2,240 PVUs required
Read: CIO Advisory: IBM sub-capacity licensing and ILMT compliance. For the ILMT tool itself, see our guide on IBM ILMT: sub-capacity licensing advisory.
5. Common Compliance Pitfalls
Eight issues that IBM audit teams actively look for
Staying compliant with IBM DB2 licensing agreements is as important as managing costs. IBM conducts regular licence audits, and common pitfalls can lead to penalties or forced purchases at list price.
| Pitfall | Risk | What Goes Wrong | Financial Impact |
|---|---|---|---|
| Under-licensing | Critical | Deploying more DB2 instances, users, or processor capacity than purchased. Often occurs when new VMs are created or users onboarded without updating licence counts. | IBM charges back-dated fees at list price plus accrued support during an audit |
| Missing ILMT | Critical | Running DB2 in virtualised environments without deploying ILMT or generating quarterly reports | IBM defaults to full-capacity licensing. 2-3x cost increase. Most common and most expensive audit finding. |
| Edition Resource Violations | High | Running DB2 Workgroup on hardware exceeding its 16-core or 128 GB RAM limits, or enabling Advanced features without the Advanced licence | Forced upgrade to Enterprise or Advanced at list price + back-support |
| User Licence Mismanagement | Medium-High | Sharing user licences between individuals or across multiple DB2 servers. Failing to meet minimum user counts per server. | Each server requires its own set of named user licences. Under-counts trigger audit findings. |
| VM Sprawl Without Controls | High | Live migrations or dynamic resourcing inadvertently increasing DB2 core allocations. New VMs spun up without ILMT coverage. | Each untracked VM is counted at full host capacity. A single missing agent can blow your compliance position. |
| Over-licensing (Shelfware) | Medium | Purchasing excessive PVU capacity “just in case” that is never utilised | Wasted budget + annual support payments (20%/year) on unused licences |
| M&A and Organisational Changes | Medium-High | Mergers or acquisitions bringing unreconciled DB2 installations. IBM may require licence transfers or new purchases. | Gap in coverage discovered during post-acquisition audit. IBM does not automatically transfer entitlements. |
| Lack of Documentation | Medium | No centralised Proof of Entitlement (PoE) records, missing ILMT reports, or no deployment inventory | Cannot defend compliance position in an audit. IBM assumes the worst case. |
💡 Fix It Before IBM Finds It
It is far cheaper to identify and remediate compliance gaps internally than to have IBM discover them during a formal audit. IBM’s audit findings typically require purchasing shortfalls at list price with no negotiation on discounts, plus backdated support fees. A proactive self-audit programme, run quarterly, can save an enterprise millions in potential audit exposure.
Received an IBM Audit Notification?
Get independent defence advice before responding. Our IBM audit specialists have defended hundreds of enterprises and saved millions in potential findings.
IBM Audit Defence Service →📄 White Paper
The IBM Audit Playbook: How to Navigate Risk, Defend Your Budget, and Stay in Control
Step-by-step audit preparation and response guide covering DB2, WebSphere, MQ, and the full IBM Passport Advantage portfolio.
Download White Paper →6. Cost Scenarios and Break-Even Analysis
Four real-world scenarios showing the financial impact of licensing decisions
Understanding the financial impact of licensing model choices and deployment decisions is critical. The difference between PVU and Authorised User licensing, and the impact of sub-capacity, can amount to hundreds of thousands of dollars.
📊 Scenario 1: Small Internal Application (15 Users, 1 Server)
Server: 1 server with 8 x86 cores (70 PVU/core = 560 PVUs total)
Option A (PVU): 560 PVUs of DB2 Enterprise. Unlimited users on this server.
Option B (Authorised User): 25 users minimum (Enterprise requires 25 per 100 PVUs; 560 PVUs rounds up to min 25 users). Even with only 15 actual users, you must buy 25.
📊 Scenario 2: Mid-Sized Deployment (200 Users, 2 Servers)
Servers: 2 servers, each with 16 x86 cores (16 x 70 = 1,120 PVUs each)
Option A (PVU): 2,240 PVUs total (1,120 x 2). Unlimited users across both servers.
Option B (Authorised User): 200 users. But each user needs a licence per DB2 instance. If users access both servers, you need 200 x 2 = 400 user licences.
📊 Scenario 3: Sub-Capacity Impact (Virtualised Environment)
Configuration: DB2 Enterprise on VMware. VM allocated 4 vCores on a host with 32 physical cores.
With ILMT (sub-capacity): 4 x 70 = 280 PVUs
Without ILMT (full capacity): 32 x 70 = 2,240 PVUs
📊 Scenario 4: Edition Overprovisioning
Situation: An enterprise deploys DB2 Advanced Enterprise for a reporting database that does not use compression, partitioning, or BLU Acceleration.
Advanced Enterprise licence cost: Significantly higher per-PVU than standard Enterprise
Enterprise Edition would suffice: Same functionality without the unused advanced features
7. Optimising and Managing DB2 Licences
Eight strategies for maximising value and avoiding overspend
| Strategy | Priority | How to Execute |
|---|---|---|
| Deploy and Maintain ILMT | Critical | Install ILMT agents on every server running IBM software. Configure weekly scans. Archive quarterly reports for 2+ years. Keep ILMT software updated with IBM’s latest catalogue. This single step can reduce PVU requirements by 50-87% in virtualised environments. |
| Right-Size DB2 Editions | Medium-High | Audit each DB2 deployment to verify which features are actually used. If Advanced features (compression, partitioning, BLU) are not required, downgrade to standard Enterprise or Workgroup. Check with IBM for conversion options. |
| Consolidate Instances | Medium | Running multiple small DB2 servers under user licences can cost more than one larger consolidated server under PVU licensing. Evaluate consolidation opportunities. Fewer servers = fewer licence points. |
| Use Developer Edition for Non-Prod | Medium | IBM provides a free DB2 Developer Edition for development and testing purposes. Use it on developer workstations and test environments instead of consuming full production licences. Ensure it is never used in production. |
| Regular Self-Audits | High | Compare DB2 usage against entitlements quarterly. Check ILMT reports, user counts, and core allocations. Identify drift early: new VMs, onboarded users, hardware upgrades. Remediate before IBM finds gaps. |
| Negotiate ELA Bundling | Variable | Enterprises with broad IBM portfolios (DB2 + WebSphere + MQ + Cognos) can negotiate Enterprise Licence Agreements for volume discounts. IBM often provides better per-PVU pricing when bundling multiple products. |
| Reclaim Idle Licences | Medium | When decommissioning servers, reclaim DB2 licences and either reallocate or stop paying support. Remove user licences from employees who no longer access DB2. This housekeeping directly reduces annual support costs. |
| Time Purchases Strategically | Medium | IBM sales teams have quarterly and annual targets. Purchasing at quarter-end (March, June, September, December) or year-end can yield additional discounts of 10-20% beyond standard volume pricing. |
📄 White Paper
10 Critical Traps in IBM Term Sheets: A Guide for CIOs and Procurement Leaders
Detailed analysis of IBM contract terms that cost enterprises millions, including auto-renewal traps, sub-capacity fine print, and ELA exit clauses.
Download White Paper →For IBM’s broader cost optimisation strategies, see our IBM cost optimisation and shelfware reduction playbook. For analytics-specific licensing, see our IBM analytics and data platform licensing playbook.
Need Independent IBM DB2 Licensing Advisory?
Redress Compliance provides vendor-independent IBM DB2 licence assessments, sub-capacity compliance reviews, audit defence, and ELA renewal advisory. We have helped hundreds of organisations reduce IBM licensing costs and avoid seven-figure audit findings.
8. Recommendations for ITAM Professionals
Seven pillars of effective IBM DB2 licence management
- AMap your environment. Maintain an up-to-date inventory of all IBM DB2 installations, including edition, version, and deployment location (physical, virtual, or cloud). Document the licensing metric (PVU or Authorised User) for each instance. This visibility is the foundation for both compliance and optimisation.
- BChoose the right metric. Select PVU or Authorised User based on actual usage patterns. For large or unpredictable user bases, PVU is almost always more suitable. For contained user groups on high-capacity servers, user licensing may be more cost-effective. Recalculate whenever usage patterns change significantly.
- CMonitor continuously with ILMT. Implement IBM ILMT and ensure it covers all servers and VMs running IBM software. Generate and archive quarterly reports. Review ILMT outputs for anomalies: unrecognised products, servers not reporting, or PVU spikes. Treat ILMT as a business-critical system.
- DConduct periodic self-audits. Internally audit IBM DB2 licences at least annually. Verify that user counts, core allocations, and edition deployments align with entitlements. Cross-reference ILMT data against IBM Passport Advantage entitlement records.
- EEducate stakeholders. Train DB2 administrators and procurement teams on the basics of IBM DB2 licensing. Ensure they understand that adding a CPU, spinning up a new VM, or onboarding users without updating licence counts has direct compliance and cost implications.
- FPlan for growth and change. Anticipate future needs. If a project will significantly increase DB2 usage, budget and acquire additional licences proactively at negotiated rates rather than at list price after an audit finding. Include licence impact assessments in M&A due diligence and data centre migration planning.
- GMaintain documentation. Keep all Proof of Entitlement documents, IBM agreements, ILMT reports, and deployment records organised and current. In an audit, complete documentation readily available is your strongest defence.
Approaching an IBM ELA renewal? Benchmark your pricing and usage before negotiating. See our IBM ELA: what you need to know before signing.
9. Action Checklist: 5 Steps to Take Now
Practical steps to get your IBM DB2 licensing under control
1Inventory Your DB2 Deployments
Document every instance of IBM DB2 in your enterprise: production, test, DR. Note the edition, version, current licensing metric (PVU or User), number of cores allocated, and number of users accessing each instance. Include cloud and containerised deployments.
2Gather Entitlements and Usage Data
Compile your IBM DB2 licence entitlements from contracts or IBM Passport Advantage reports. Simultaneously, measure current usage: total PVUs on each server and authorised user counts per instance. Ensure ILMT is capturing virtualised environments accurately.
3Compare and Identify Gaps
Compare usage data against entitlements. Highlight under-licensed areas (e.g. a server consuming 800 PVUs but only 720 purchased, or 50 users on a system with 30 licences) for immediate remediation. Also note significant over-licensing where you have surplus capacity.
4Remediate and Optimise
For shortfalls, develop a plan: purchase additional licences or reduce usage (scale down VM core allocations). For surpluses, reassign or retire licences to save on support. Verify ILMT is correctly deployed, generating quarterly reports, and covering every IBM software host.
5Implement Ongoing Governance
Establish a governance process: require change management approval for any DB2 deployment changes (to assess licence impact), schedule regular internal audits, and update documentation whenever infrastructure changes. This discipline keeps IBM DB2 licensing under control and ensures audit readiness.
📄 White Paper
The Hidden Cost of IULA: Are You Paying Twice for Global Use?
Analysis of IBM International Unlimited Licence Agreements and how enterprises unknowingly overpay through overlapping entitlements and geographic restrictions.
Download White Paper →10. Frequently Asked Questions
Common questions about IBM DB2 licensing
IBM DB2 can be licensed primarily in two ways: Processor Value Unit (PVU) or Authorised User. PVU licensing is based on the number of CPU cores and their IBM-assigned PVU values (e.g. most x86 cores = 70 PVU). It allows unlimited user access on licensed machines. Authorised User licensing counts named individuals who access DB2, with minimum quantities (e.g. 5 users per server for Workgroup, 25 users per 100 PVUs for Enterprise). For DB2 Connect (mainframe access), IBM also offers concurrent user bundles of 25. The vast majority of enterprise DB2 deployments use PVU licensing for flexibility and cost-efficiency at scale.
Use PVU licensing if you have a large or fluctuating number of users, or if the application is web-facing where counting individual users is impractical. PVU is also required for sub-capacity benefits in virtualised environments. Choose Authorised User licensing if you have a small, defined, stable user population on a relatively large server, for example 20 users on a 16-core server. The break-even depends on IBM’s per-PVU and per-user pricing in your agreement, but generally, once user counts exceed 30-40 per server, PVU becomes more cost-effective. Always calculate both scenarios before committing, and factor in user growth projections.
Sub-capacity licensing allows you to licence IBM DB2 on only part of a server’s capacity when using virtualisation. For example, licensing just the 4 virtual cores allocated to a DB2 VM rather than the full 32-core physical host. This can reduce PVU requirements by 75-90%. However, IBM mandates deployment of the IBM Licence Metric Tool (ILMT) within 90 days of installation to qualify. ILMT must run weekly scans, cover every IBM software host, and generate quarterly reports archived for 2+ years. Without ILMT, IBM’s policy is full-capacity licensing: you must licence all physical cores, potentially multiplying costs 2-4x. There are no exceptions.
Yes. IBM sets minimum licence counts for DB2. For Authorised User licensing, DB2 Workgroup Edition requires at least 5 user licences per server. DB2 Enterprise Edition typically requires at least 25 user licences for every 100 PVUs of server capacity. IBM DB2 Connect concurrent user licences are sold in fixed blocks of 25 users. User licences are tied to one named individual and one installation. They cannot be shared across servers or individuals (except for permanent personnel changes). On the PVU side, you must licence all active cores where DB2 is installed (or the sub-capacity VM allocation if ILMT qualifies). IBM also permits one cold standby installation for DR under the primary licence, but the terms are specific and the backup must remain idle except during failovers or brief tests.
Match the edition to your technical requirements. Workgroup is appropriate for department-level databases that stay within 16 cores and 128 GB RAM. Enterprise is for mission-critical production systems requiring unlimited scalability and high availability. Advanced editions add compression, partitioning, and BLU Acceleration analytics capabilities. Only choose these if you actively use those features. Deploying Workgroup on hardware that exceeds its resource limits is a licence violation. If your environment might grow beyond Workgroup limits, budget for an Enterprise upgrade path. IBM’s free Developer Edition is available for non-production development and testing.
Several strategies can optimise costs. Right-size and consolidate: avoid running many under-utilised DB2 servers. One larger instance under PVU licensing may be cheaper than multiple small ones. Use appropriate editions: do not pay for Advanced features you do not use. Leverage sub-capacity: deploy ILMT and licence only VM-allocated cores. Monitor and reclaim: track usage and remove idle licences to stop paying support on shelfware. Negotiate renewals: request volume discounts, multi-year commitments, or ELA bundling. Time purchases to IBM quarter-ends for additional leverage. Stay compliant: avoiding audit penalties is itself a major cost-saving measure.
IBM has the contractual right to audit your compliance, typically with 30 days’ notice. They may use internal audit teams or the IBM Authorised SAM Provider (IASP) programme. During an audit, IBM will request your Proof of Entitlement documents, ILMT reports (quarterly archives), and a complete inventory of DB2 deployments. They compare your actual usage against purchased entitlements. Common findings include missing ILMT (triggering full-capacity charges), edition misuse, under-licensed cores or users, and unlicensed non-production environments. Audit findings typically require purchasing shortfalls at list price plus backdated support fees. The best defence is proactive compliance.
IBM offers DB2 in subscription-based models for cloud and container environments (e.g. DB2 Direct Standard/Advanced Edition). These are licensed on a flexible basis: monthly subscriptions, virtual CPU counts, or IBM Cloud Pak credits, rather than traditional perpetual PVU or user licences. For bring-your-own-licence (BYOL) scenarios on AWS, Azure, or other clouds, the same sub-capacity rules apply: you must deploy ILMT agents on cloud VMs to track PVU/VPC usage. IBM Cloud Pak for Data can bundle DB2 with other data tools under a unified VPC metric. For details on the PVU-to-VPC transition, read our CIO Playbook: IBM PVU-to-VPC licensing transition.