On Linux environments where:
- license restricts number of cores available for DB2,
DB2 might be incorrectly limited to the smaller subset of cores
than the license enforces. As the result, following message will
be logged to db2diag.log:
(example for SMT=8)
2016-08-17-10.21.35.550156+120 E6338E393 LEVEL: Info
PID : 126000 TID : 70366688899504 PROC :
db2sysc
INSTANCE: db2inst1 NODE : 000
HOSTNAME: db2host
FUNCTION: DB2 UDB, oper system services,
sqloPerformCPUBindingForDB2, probe:5
MESSAGE : ADM0517W CPU binding information: DB2 member
processes are bound to
"2" cores.
2016-08-17-10.21.35.571301+120 E6732E506 LEVEL:
Warning
PID : 126000 TID : 70366688899504 PROC :
db2sysc
INSTANCE: db2inst1 NODE : 000
HOSTNAME: db2host
FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:17
DATA #1 : String, 64 bytes
Due to the license limitation, the instance is limited to cores:
DATA #2 : signed integer, 8 bytes
16
DATA #3 : String, 28 bytes
Memory usage is limited to:
DATA #4 : signed integer, 8 bytes
137438953472
and DB2 will not utilize all CPU cores that should be available
for given license.
The message about the number of cores, to which DB2 is limited,
is correct (16 in the case above), but binding is done to two
physical cores, which is incorrect because license restriction
should be enforced for physical cores and not CPU threads.
One of the environments affected is DB2 running on POWER8
PPC64LE, under PowerVM hypervisor. |
