|
Problem IC87864
|
Status: Closed |
THE NO_SORT_NLJOIN AND NO_SORT_MGJOIN DB2_REDUCED_OPTIMIZATION OPTIONS ARE NOT CONSIDERED AT OPT LEVEL 7 |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
The NO_SORT_NLJOIN and NO_SORT_MGJOIN options for the
DB2_REDUCED_OPTIMIZATION registry variable are not considered
at opt level 7. At the lower opt levels, these settings
will disable planning for sorted NLJOINs and sorted MSJOINs. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1 Fix Pack 2 *
**************************************************************** |
| Local Fix: |
Use an optimization profile to force the join method / order
that is equivalent the plan when the NO_SORT setting is in
effect. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in version 10.1 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.11.2012
17.12.2012
17.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
