IBM Db2 Licensing

Independence statement. IBM Licensing Experts is an independent advisory firm. We are not an IBM Business Partner, reseller, or affiliate. We have no resell margin tied to our recommendations and we do not earn revenue from any IBM product line. Read more on why independence matters.

Why Db2 licensing is consequential.

Db2 sits inside the most regulated workloads in a typical enterprise (the system of record databases, the analytical warehouses, the operational data stores). The compliance gap on Db2 is therefore both expensive and visible. The two recurring failure modes are the edition gap (Standard edition deployed but Advanced features in use) and the metric gap (Authorized User entitlement on a workload that has grown beyond the named user inventory). Both are preventable with operational discipline. See database expertise page for the cross cluster frame.

1. The Db2 edition tree.

The current Db2 distributed edition tree is Db2 Advanced Server, Db2 Standard, Db2 Workgroup, and the free Db2 Community Edition. Each edition has a defined feature set and a defined entitlement profile. Advanced Server is the comprehensive edition. Standard is the production grade core. Workgroup is sized for departmental deployment. Community is the developer edition without production licensing.

The buyer side discipline is to verify the edition deployed on each Db2 instance and to reconcile the deployed edition against the licensed edition at least annually. An edition mismatch on a high transaction Db2 instance is a six to seven figure compliance gap. See Db2 Licensing Explained white paper for the full edition matrix.

2. PVU versus Authorized User.

Db2 is sold under two metrics. PVU (Processor Value Unit) on the workload footprint, which is the typical enterprise deployment. Authorized User on a per named user basis, which fits the lower volume analytical and developer use cases. The same Db2 edition is available under both metrics. The choice at procurement decides the audit conversation for the lifetime of the deployment.

The PVU model is sub capacity eligible and is the right choice for most enterprise workload. The Authorized User model is the right choice when the user inventory is small, stable, and known. The decision should not be inherited from a legacy procurement. See PVU explained for the metric reading.

3. The feature gating.

Db2 Standard and Db2 Advanced Server are differentiated by the included features. Federation (the ability to read data from non Db2 sources), Replication (the data movement capability), Db2 Advanced Recovery (the backup and restore tooling beyond the standard backup), and Db2 Advanced Security (the data masking and row level security) are Advanced Server features. The use of any one of them on a Standard edition entitlement is the Advanced edition compliance gap.

The most common Db2 compliance gapDb2 Standard licensed in 2018. The DBA team has since enabled Federation to read from an Oracle data source and Replication to feed a downstream warehouse. The licensing was not revisited. The audit reads the system catalog, identifies the Federation and Replication usage, and produces an Advanced Server upgrade finding for the entire workload. The settlement is the Advanced Server price differential applied retrospectively across the period the features were in use.

The buyer side discipline is the annual Db2 feature audit. Read the system catalog on each Db2 instance, list the enabled features, reconcile the feature use against the licensed edition. The work is one DBA hour per instance and prevents the largest single Db2 audit finding. See self assessment guide for the formal process.

4. Sub capacity and Db2.

Db2 PVU is sub capacity eligible on the recognised virtualization platforms. The ILMT discipline applies in full. The Db2 specific consideration is that the Db2 process footprint must be measurable by ILMT. A Db2 instance that runs in a configuration ILMT cannot enumerate (the rare custom binary install in a non standard path, or a container without the ILMT scanner) is counted at full capacity. See ILMT guide and sub capacity explained.

5. Db2 on containers and Cloud Pak.

Db2 has a container deployment and a Cloud Pak for Data bundling. The container deployment uses the standard Db2 binary in an IBM published container image and is metered by the IBM License Service. The Cloud Pak for Data bundling includes Db2 as a service inside the Cloud Pak entitlement frame. The two are not interchangeable for licensing purposes. A Db2 standalone container deployment continues to draw down the Db2 entitlement. A Cloud Pak for Data deployment of Db2 draws down the Cloud Pak entitlement. See container licensing for the model and Cloud Pak strategy for the bundling calculus.

6. Db2 for z/OS.

Db2 for z/OS is a distinct product. It is licensed under the mainframe MLC envelope and the MSU four hour rolling peak captured by SCRT. It is not interchangeable with the distributed Db2 entitlements. A buyer with both estates runs the distributed and mainframe Db2 entitlements in parallel and reconciles them separately. See product licensing guide and the mainframe expertise page.

7. Audit posture on Db2.

Db2 inside an audit is reconciled on three axes. The deployed edition against the licensed edition (the edition gap above). The deployed metric against the licensed metric (the user inventory against the Authorized User entitlement). The deployed footprint against the PVU entitlement (the standard sub capacity reconciliation). All three are read by the auditor in the same engagement.

The buyer side defence is the prepared evidence package on all three axes. The deployed edition with the feature catalog reading. The user inventory with the Authorized User reconciliation. The ILMT Audit Snapshot for the PVU footprint. The package is reviewed before the audit data submission and any finding is anticipated, costed, and dealt with on the buyer side schedule. See audit defense playbook and audit defense service.

Ready to put this work into practice?

An independent senior advisor on your IBM estate. No resell margin, no IBM relationship to protect, no time pressure to push a product. Just the buyer side view.

Schedule a consultation All services

IBM Db2 Licensing.