DB2 - Problem description
Problem IC81675 | 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 / 950 - 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.5 FP10 or subsequent fix packs. * **************************************************************** | |
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. | |
Solution | |
Problem First Fixed in DB2 Version 9.5 Fix Pack 10 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC83597 IC87864 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.02.2012 06.11.2012 06.11.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP10 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.10 |