Db2 Warehouse and Cloud Pak for Data conversion.

What the conversion actually changes

Db2 Warehouse on its own is licensed on a core based basis, and many estates still hold entitlements expressed that way. Once the workload is delivered through Cloud Pak for Data, the same database capability is consumed as a containerized service on the platform, and the platform is metered in Virtual Processor Core. The conversion is not a like for like swap of one unit for another. It restates your existing entitlement into VPC through a defined ratio, and it folds the deployment into a container platform whose compliance rules differ from a standalone install. Treating the move as a simple rename is how organizations lose track of what they are actually entitled to.

VPC and the post v11 sub-capacity rules

Virtual Processor Core became subject to ILMT based sub-capacity reporting under Passport Advantage version 11, which applied to existing customers from May 1 2023. That matters here because the older assumption, that you could count Cloud Pak capacity by hand or estimate it, no longer holds. VPC metered products require the same continuous ILMT measurement that core based products do. If the Cloud Pak deployment is not being measured properly, the sub-capacity position is exposed in exactly the way a traditional Db2 install would be, and the container rules make the consequence harsher.

The container charging trap

On a container platform, non compliance does not stay contained to the workload that drifted. Where the Cloud Pak deployment cannot demonstrate a clean sub-capacity position, IBM can charge for all of the cores in the cluster, not only the cores running Db2 Warehouse. A small measurement gap in one namespace can therefore scale into a claim sized against the whole cluster. This is the single most expensive way a Cloud Pak for Data conversion goes wrong, and it is also one of the most reversible, because it usually rests on a measurement deficiency rather than a genuine over deployment.

Where the conversion math is contestable

Two numbers decide the exposure: the ratio used to convert your prior Db2 Warehouse entitlement into VPC, and the VPC count the platform is actually consuming. An audit can apply an unfavorable or simply incorrect ratio, ignore entitlement that should have carried across the conversion, or count cluster wide capacity where a clean sub-capacity position would have limited the count. Rebuilding the entitlement carryover and proving the measured VPC from platform data is how each of those is challenged. The defense is methodical rather than dramatic: confirm the ratio, credit the entitlement that converted across, and prove the sub-capacity position from the platform metering.