DB2 - Problem description
Problem IC64199 | Status: Closed |
ENABLING REGISTRY VARIABLE DB2_EXTENDED_OPTIMIZATION=IXOR UNDER THE DB2_WORKLOAD=SAP AGGREGATED REGISTRY VARIABLE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
For SAP applications, we recommend to set DB2_EXTENDED_OPTIMIZATION=IXOR registry variable to performance enhancement. This is going to be enabled under the aggreated registry variable DB2_WORKLOAD=SAP in v91FP9, v95FP6, v97FP2 and later releases. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * For SAP applications, we recommend to * * setDB2_EXTENDED_OPTIMIZATION=IXOR registry variable * * toperformanceenhancement. This is going to be enabled under * * theaggregatedregistry variable DB2_WORKLOAD=SAP in v91FP9, * * v95FP6, v97FP2andlater releases. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 2 * **************************************************************** | |
Local Fix: | |
You may turn on the registry variable DB2_EXTENDED_OPTIMIZATION=IXOR by itself. db2set DB2_EXTENDED_OPTIMIZATION=IXOR | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 Fix Pack 2 | |
Workaround | |
You may turn on the registry variable DB2_EXTENDED_OPTIMIZATION=IXOR by itself. db2set DB2_EXTENDED_OPTIMIZATION=IXOR | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.10.2009 30.06.2010 30.06.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP2 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |