Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC91811 Status: Geschlossen

DB2 CAN TRAP WHEN COMPILING A SUB-QUERY that is APPLIED ON XMLQUERY()

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
DB2 can trap when it compiles a SQL query that has a sub-query 
applied on XMLQUERY(), and the query block that contains the 
sub-query has more than 64 predicates. 
 
The following is an example of the sub-query: 
 
XMLCAST(XMLQUERY(...)   AS CHAR(8)) IN (SELECT X FROM TABLE1) 
 
 
It can generate the stack traces below: 
 
-------------- Stack Trace ------------------------- 
sqlno_copy_plan_map 
copy_plan_args 
sqlno_copy_function_args 
sqlno_copy_plan__FCP13sqlno 
sqlno_crule_save_plans 
sqlno_crule_access 
sqlno_crule_access 
sqlno_find_plan_chain 
sqlno_get_best_plan 
sqlno_crule_nljn_inner 
sqlno_crule_nljn 
sqlno_crule_join_choices 
sqlno_crule_join_order 
sqlno_crule_join_root 
sqlno_crule_join 
sqlno_gen_partitions_for_QTB 
sqlno_plan_end_opr 
sqlno_each_opr 
sqlno_walk_qun 
sqlno_each_opr 
sqlno_top_qtb 
sqlno_each_qur 
sqlno_scan_qgm 
sqlno_planning_scan 
sqlno_planning_phase 
sqlno_exe 
sqlno_exe 
sqlnn_cmpl 
sqlnn_cmpl 
sqlra_compile_var 
sqlra_find_var 
sqlra_get_var 
sqlrr_prepare 
sqljs_ddm_prpsqlstt 
sqljsParseRdbAccessed 
sqljsParse.fdpr.clone.77 
@63@sqljsSqlam 
@63@sqljsDriveRequests 
@63@sqljsDrdaAsInnerDriver 
sqljsDrdaAsDriver 
RunEDU 
EDUDriver 
sqloEDUEntry 
 
-------------- Stack Trace ------------------------- 
pthread_kill 
sqloDumpEDU 
sqle_panic 
sqle_trap 
sqlzAssertFailedValist 
sqlzAssertFailed 
sqlo_md_mcpy 
sqlno_copy_setN 
sqlno_difference_setsN 
sqlno_difference_set 
sqlno_prop_preds 
sqlno_prop_filter 
FILTER__FP13sqlno 
sqlno_crule_xscan 
sqlno_crule_access_root 
sqlno_crule_access 
sqlno_find_plan_chain 
sqlno_get_best_plan 
sqlno_get_best_plan 
sqlno_crule_nljn_inner 
sqlno_crule_nljn 
sqlno_crule_join_choices 
sqlno_crule_join_order 
sqlno_crule_join_root 
sqlno_crule_join 
sqlno_gen_partitions_for_QTB 
sqlno_plan_end_opr 
sqlno_call_sf 
sqlno_each_opr 
sqlno_call_sf 
sqlno_walk_qun 
sqlno_call_sf 
sqlno_each_opr 
sqlno_call_sf 
sqlno_top_qtb 
sqlno_call_sf 
sqlno_each_qur 
sqlno_call_sf 
sqlno_scan_qgm 
sqlno_planning_scan 
sqlno_planning_phase 
sqlno_exe 
sqlnn_cmpl 
sqlnn_cmpl 
sqlra_compile_var 
sqlra_find_var 
sqlra_get_var 
sqlrr_prepare 
sqljs_ddm_prpsqlstt 
sqljsParseRdbAccessed 
sqljsParse 
sqljsSqlam 
sqljsDriveRequests 
sqljsDrdaAsInnerDriver 
sqljsDrdaAsDriver 
RunEDU 
EDUDriver 
sqlzRunEDU 
qloEDUEntry 
 
----------------------------------- 
 
On DB2 9.7FP8 it can generat a FODC application error with the 
stack below, however the DB2 instance doesn't crash. 
 
-------------- Stack Trace ------------------------- 
pthread_kill 
sqloDumpEDU 
sqldDumpContext 
sqldDumpContext 
sqlrr_dump_ffdc 
sqlzeDumpFFDC 
sqlzeSqlCode 
sqlnn_erds 
sqlnn_erds 
sqlno_copy_function_args 
sqlno_copy_plan 
sqlno_copy_plan_map 
copy_plan_args 
sqlno_copy_function_args 
sqlno_copy_plan 
sqlno_crule_save_plans 
sqlno_crule_access 
sqlno_crule_access 
sqlno_find_plan_chain 
sqlno_get_best_plan 
sqlno_crule_nljn_inner 
sqlno_crule_nljn 
sqlno_crule_join_choices 
sqlno_crule_join_order 
sqlno_crule_join_root 
sqlno_crule_join 
sqlno_gen_partitions_for_QTB 
sqlno_plan_end_opr 
sqlno_each_opr 
sqlno_walk_qun 
sqlno_each_opr 
sqlno_top_qtb 
sqlno_each_qur 
sqlno_scan_qgm 
sqlno_planning_scan 
sqlno_planning_phase 
sqlno_exe 
sqlno_exe 
sqlnn_cmpl 
sqlra_compile_var 
sqlra_find_var 
sqlra_get_var 
sqlrr_prepare 
sqljs_ddm_prpsqlstt 
sqljsParseRdbAccessed 
sqljsParse.fdpr.clone.0 
@63@sqljsSqlam 
@63@sqljsDriveRequests 
@63@sqljsDrdaAsInnerDriver 
RunEDU 
EDUDriver 
sqloEDUEntry 
 
----------------------------------- 
 
 
 
There is no workaround.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 3                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Version 10.1 Fix Pack 3.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.04.2013
08.10.2013
08.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList