DB2 - Problem description
Problem IC94337 | Status: Closed |
QUERY ON VARCHAR2 ENABLED DATABASE NO LONGER USES INDEX SCAN AFTER UPGRADE TO FIX PACKS 5 TO 8 | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
A query that may have been perfoming well prior to DB2 version 9.7 fix pack 5 may stop choosing an index after upgrading to DB2 version 9.7 fix packs 5 to 8. This can happen on a VARCHAR2 enabled database when the query includes basic predicates involving VARCHAR columns. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users on version 9.7 fix packs 5 to 8 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.7 fix pack 9 * **************************************************************** | |
Local Fix: | |
Use optimization guidelines to use the appropriate index, for example: SELECT... /* <OPTGUIDELINES> <IXSCAN TABLE="A" INDEX="MYINDEX"/> </OPTGUIDELINES> */ | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 version 9.7 fix pack 9 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC96232 IC96236 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.07.2013 02.01.2014 02.01.2014 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.9 | |
9.7.0.9 |