suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT21441 Status: Closed

PROCESSOR SPECIFIC OPTIMIZATIONS ARE NOT USED AS EXPECTED

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Db2 contains processor specific optimizations. They get only 
enabled, if a suitable processor gets detected. 
While a line like this in db2diag.log can be found that 
indicates that DB2 has detected a SSE4 capable CPU: 
 
CPU: total:32 online:32 Cores per socket:8 Threading degree per 
core:2 SIMD:Y CPU Features:SSSE3,SSE4 
 
another line in db2diag.log indicates that the CPU optimizations 
are effectively not used: 
 
BLU: HW SIMD enabled: SCAN(Y), ARITH(Y), COMP(Y), CPU(1) 
 
That means only SSE2 optimizations are used.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All systems with modern CPUs.                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade Db2.                                                 * 
****************************************************************
Local Fix:
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.07.2017
21.07.2017
21.07.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)