DB2 - Problembeschreibung
Problem IC63234 | Status: Geschlossen |
INSTANCE CRASH DURING QUERY EXECUTION WHEN QUERY CONTAINS "LIKE"OPERATOR AGAINST RANGE PARTITIONED TABLE. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
If a query is run that contains: - at least 2 predicates against a range partitioned table - 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. Then this problem may happen. It is a crash with the following signal #11 stack traceback: sqlriSectInvoke + 0x4 sqlrr_process_execute_request + 0x1EC sqlrr_execute - 0xF8 sqljs_ddm_excsqlstt + 0x46C sqljsParseRdbAccessed - 0x48 sqljsParse + 0x140 sqljsSqlam + 0xD4 sqljsDriveRequests + 0xA4 sqljsDrdaAsInnerDriver + 0xD4 sqljsDrdaAsDriver + 0x9C sqleRunAgent + 0x36C The cause of the problem is due to a logic error during the phase of query compile that constructs the executable form of the query called a "section". The problem is that there is a memory overwrite that corrupts part of the section. Since this is a memory overwrite type of problem, the above stack may just be one of the possible symptoms. Other symptoms may also be possible depending on the details of the query and which part of it ends up getting corrupted. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL. * **************************************************************** * PROBLEM DESCRIPTION: * * INSTANCE CRASH DURING QUERY EXECUTION WHEN QUERY CONTAINS * * "LIKE" OPERATOR AGAINST RANGE PARTITIONED TABLE. * * * * * * If a query is run that contains: * * - at least 2 predicates against a range partitioned table * * - 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. * * * * Then this problem may happen. It is a crash with the * * following signal #11 stack traceback: * * * * sqlriSectInvoke + 0x4 * * sqlrr_process_execute_request + 0x1EC * * sqlrr_execute - 0xF8 * * sqljs_ddm_excsqlstt + 0x46C * * sqljsParseRdbAccessed - 0x48 * * sqljsParse + 0x140 * * sqljsSqlam + 0xD4 * * sqljsDriveRequests + 0xA4 * * sqljsDrdaAsInnerDriver + 0xD4 * * sqljsDrdaAsDriver + 0x9C * * sqleRunAgent + 0x36C * * * * The cause of the problem is due to a logic error during the * * phase of query compile that constructs the executable form * * of the query called a "section". The problem is that there * * is a memory overwrite that corrupts part of the section. * * * * Since this is a memory overwrite type of problem, the above * * stack may just be one of the possible symptoms. Other * * symptoms may also be possible depending on the details of * * the query and which part of it ends up getting corrupted. * **************************************************************** * RECOMMENDATION: * * Upgrade to version 9.7 fixpack 1 or later fixpack. * **************************************************************** | |
Local-Fix: | |
Modify SQL statement to break the conditions described in the APAR description. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
This problem is first fixed in version 9.7 fixpack 1 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 21.09.2009 24.02.2010 24.02.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP1 | |
Problem behoben lt. FixList in der Version | |
9.7.0.1 |