DB2 - Problem description
Problem IT21806 | Status: Closed |
JUMP SCAN MAY GET SIGSEGV AT SQLNO_PLAN_ARGS_SCAN | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Here is a sample stack trace back, from a trap file: --- sqlno_copy_plan_map copy_plan_args sqlno_copy_function_args sqlno_copy_plan sqlno_copy_function_args --- This problem was introduced in V10.1 GA, with the jump scan feature. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Db2 Version 11.1 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 Version 11.1 Mod 2 Fix Pack 2. * **************************************************************** | |
Local Fix: | |
Disable jump scan by applying an optimization profile on this query. | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT17664 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.08.2017 10.10.2017 10.10.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |