db2 applying licensing file produces two licenses

All we need is an easy explanation of the problem, so here it is.

  1. I installed Db2 from fixpack v11.5.7.0 using db2_install command.
  2. I have downloaded "IBM Db2 Advanced Edition – VPC Option V11.5.6 – Activation (CC9WHML)" file from IBM Passport Advantage.
  3. I have applied license with: db2licm -a <license_file>
  4. I have checked applied license: db2licm -l and output is:
Product name:                     "DB2 Community Edition"
License type:                     "Community"
Expiry date:                      "Permanent"
Product identifier:               "db2dec"
Version information:              "11.5"
Max amount of memory (GB):        "16"
Max number of cores:              "4"
Features:
IBM DB2 Performance Management Offering:              "Not licensed"

Product name:                     "DB2 Advanced Edition"
License type:                     "Virtual Processor Core"
Expiry date:                      "Permanent"
Product identifier:               "db2adv"
Version information:              "11.5"
Enforcement policy:               "Hard Stop"
Features:
IBM DB2 Performance Management Offering:              "Not licensed"

I haven’t seen this kind of display before. Looks like two licenses are applied "Community" and "Advance" edition.

Questions:

a) Is it OK that two licenses are displayed? Which one is valid, both?

b) At "Advanced" edition section what does "Enforcement policy" of "Hard Stop" relates to? Until now I have always seen only "Soft Stop". Like I see "Advance" edition has no CPU cores limitations, so what does "Hard Stop" means at this license?

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

I’ve noticed the same thing and I guess that the licence for the community edition is applied always, just in case. In the deploy job, I just remove that one before adding the one that I’m entitled to:

db2licm -r db2dec
db2licm -a <licence>

I don’t think it matters (but I don’t know for sure) that the community edition is there. AFAIK, there are no complaints from the compliance report:

db2licm -g <filename>

if you have both. It is however more convenient – for me – if there is one licence on each server (I collect that and other info from all servers on a regular basis and create a report out of it).

A hard stop usually means that things will stop working if you violate the licence. If you for example use any functionality from the "IBM DB2 Performance Management Offering" you probably will notice. A soft stop usually means you will get noticed of the violation, but things will continue to work.

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply