DB2 - Problem description
Problem IT17497 | Status: Closed |
DB2 MAY TRAP WHEN RUNNING A QUERY AGAINST A DATA PARTITIONED TABLE THAT CONTAINS A PREDICATE WITH LIKE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
FODC/TRAP with following sql a query is run that contains: - at least 2 predicates against a range partitioned table OR a predicate and a join on the range partitioned table both on the same column - One of the predicates is of the form "columnName LIKE 'value'" (i.e. the LIKE keyword is used) - the column for the predicate is the range column in the partitioned table. - there is an index on the range column. problem can be recreated like create table rangetable (rangecolumn char(10) not null with default ' ') partition by range (rangecolumn) (part "part1" starting('100'), part "part2" starting('101') ending(maxvalue)); alter table rangetable add primary key (rangecolumn); select rangecolumn from rangetable where rangecolumn like ? and (substr(rangecolumn,5,2) = '99' or substr(rangecolumn,5,2) = '13'); When trap, the stack looks like: <StackTrace> sqlriUpdateIndexSSKey @51@sqlri_likePatPadit sqlri_like_patPadLow sqlriSectInvoke @97@sqlrr_process_open_request sqlrr_open sqljsParseRdbAccessed @72@sqljsSqlam @72@sqljsSqlam @72@sqljsSqlam @72@sqljsDriveRequests @72@sqljsDrdaAsInnerDriver RunEDU RunEDU EDUDriver sqloEDUEntry </StackTrace> | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 10.5 Fix Pack 9 or higher * **************************************************************** | |
Local Fix: | |
Solution | |
First fixed in Db2 10.5 Fix Pack 9 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.10.2016 29.09.2017 29.09.2017 |
Problem solved at the following versions (IBM BugInfos) | |
9.0. | |
Problem solved according to the fixlist(s) of the following version(s) |