|
Problem IC83597
|
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 / 970 - 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 9.7 FP7 or subsequent fix pack *
**************************************************************** |
| 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 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem First Fixed in DB2 Version 9.7 Fix Pack 7 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.05.2012
01.11.2012
01.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP7
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.7
|
 |
