|
Problem IT17664
|
Status: Closed |
JUMP SCAN MAY GET SIGSEGV AT SQLNO_PLAN_ARGS_SCAN |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - 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 UDB Version 10.5 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 10.5 FixPack 9. *
**************************************************************** |
| Local Fix: |
Disable jump scan by applying an optimization profile on this
query.
<OPTGUIDELINES>
<REGISTRY>
<OPTION NAME='DB2_REDUCED_OPTIMIZATION' VALUE='JUMPSCAN OFF'/>
</REGISTRY>
</OPTGUIDELINES> |
| Solution |
Problem was first fixed in DB2 UDB Version 10.5 FixPack 9. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.10.2016
27.09.2017
27.09.2017 |
| Problem solved at the following versions (IBM BugInfos) |
9.0.
|
| Problem solved according to the fixlist(s) of the following version(s) |
