Starting Db2 v11.5 , licensing tool
db2licm has the option "
-m" , to lower processor core limit
( see
https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0002451.html )
-m product-identifier num-cores
"Updates the number of cores entitlements that the customer has purchased for record keeping. Specify the product identifier and the number of cores. Note that there is no enforcement on the actual number of cores."At all times, one should be legal (and technical) compliant ; only use the max number of PVU/VPC's purchased.
(let's say, purchased 1x Virtual Processor Core (VPC) license key, entitled to use for max 50 vCPU's , on many (virtual) servers on-premise / of-premise. one can have a (virtual) server with 12x vCPU's , then with db2licm add VPC license key , and lower cores to f.i. 4x cores .... But then cannot restrict Db2 instances using max 4 cores, not legally nor technically (on Linux/RHEL) ?
Why, with db2licm, would one actually want to 'limit' the cores on a Db2 server installation (for a specific Edition), if it is
not enforced when one actually
uses the Db2 product ? For just 'record' keeping only seems useless to me.
------------------------------
Erwin Hattingh
Systems Engineer / Db2 DBA
Triodos Bank
------------------------------
#Db2