JR26958: DB2LICM -L SHOWS WRONG NUMBER OF PROCESSORS ON THE SYSTEM WITH DUAL CORE AND HYPERTHREADING ENABLE CPU

DB2 UDB Version 8.1 FixPak 16 (also known as Version 8.2 FixPak 9 )

APAR status

• Closed as program error.

Error description

• If you try to run "db2licm -l" on the system which has a dual
  core cpu supporting hyperthreading, you will see Number of
  processors = "0" output as follows.
  
    And at this time, you will also see "Cores per socket:2
  Threading degree per core:4" message in db2diag.log and this is
  the eye-catcher for this APAR.
  
  
  db2licm -l output
  
  Product Name                  = "DB2 Workgroup Server Unlimited
  Edition"
  Product Password              = "DB2WSUE"
  Version Information           = "8.2"
  Expiry Date                   = "Permanent"
  Number of processors          = "0"
  Number of licensed processors = "2"
  Annotation                    = ""
  Other information             = ""
  
  
  db2diag.log
  
  2007-06-05-16.58.37.843000+540 E27620F858         LEVEL: Event
  PID     : 2140                 TID  : 1864        PROC :
  db2syscs.exe
  INSTANCE: DB2                  NODE : 000
  FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
  MESSAGE : ADM7513W  Database manager has started.
  START   : DB2 DBM
  DATA #1 : Build Level, 144 bytes
  Instance "DB2" uses "64" bits and DB2 code release "SQL08025"
  with level identifier "03060106".
  Informational tokens are "DB2 v8.1.12.99", "s060429", "WR21370",
  FixPak "12".
  DATA #2 : System Info, 1568 bytes
  System: WIN32_NT HQNS000283 Service Pack 2 5.2 AMD64 Family 15,
  model 6, stepping 8
  CPU: total:4 online:4 Cores per socket:2 Threading degree per
  core:4
  Physical Memory(MB): total:8188 free:7220 available:7220
  Virtual  Memory(MB): total:9794 free:16520
  Swap     Memory(MB): total:1606 free:9300
  

Local fix

• Not available
  

Problem summary

• db2licm -l shows wrong number of processors on the system with
  dual core and hyperthreading enabled cpu.  And wrong number of
  "Threading degree per core" in CPU information of db2diag.log
  START DB2 DBM event.
  

Problem conclusion

• Problem was first fixed in Version 8.1 FixPak 16 (a.k.a. Version
  8.2 FixPak 6)
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  IZ07215 JR27681 JR27682

Modules/Macros

• engn_sqo
  

Fix information

• Fixed component name

  DB2 UDB WSUE WI

• Fixed component ID

  5765F4301

Applicable component levels

• R810 PSN

     UP

• R820 PSN

     UP