|
Problem IT24078
|
Status: Closed |
DB2 MAY HIT SUSTAINABLE TRAP IN SQLNO_CREATE_TEMPORAL_KEYS PROCESSING
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
Problem happens in function that analyzes a temporal table
access. The problem can be hit if the query contains AS OF
predicates and there are more than 1 BTWO (Business time without
overlap) indexes on the table. Even if these conditions are
satisfied, it isn't guaranteed a user will hit the issue.
The trap is sustainable, and top of the FODC stack is following:
sqlno_exists_in_setP__FP13sqlno_globalsP9sqlno_sdbi9sqlno_set +
0xF8
sqlno_create_temporal_keys__FP13sqlno_globalsP9sqlno_qtbP11sqlno
_tableP21sqlno_plan_properties13SQLNN_BOOLEANP16sqlno_listheader
T4bPP16sqlno_listheader + 0x1064
sqlno_key_build_prop__FP13sqlno_globalsP11sqlno_tableP21sqlno_pl
an_properties + 0xCF8
sqlno_prop_table_init__FP13sqlno_globalsP21sqlno_plan_properties
P17sqlno_access_path9sqlno_setP10sqlno_partT4P18sqlno_join_conte
xtP13SQLNN_BOOLEANb + 0x1C80
sqlno_prop_iscan__FP13sqlno_globalsP13sqlno_contextP21sqlno_plan
_propertiesP19sqlno_plan_function + 0x348
ISCAN__FP13sqlno_globalsP13sqlno_contextP17sqlno_access_pathP16s
qlno_dpart_elim9sqlno_setT5P16sqlno_ixkeycondsT7T5P20sqlno_qun2p
lan_array13SQLNN_BOOLEANT5fPP19sqlno_plan_operatorUsT11_P10sqlno
_partN211_b + 0x464
... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher *
**************************************************************** |
| Local Fix: |
NA |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.02.2018
27.11.2018
27.11.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
