home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC76434 Status: Geschlossen

QUERY MAY FAIL WITH A -901 WHEN OPTIMIZER TRIES TO MERGE MULTIPLE UNION
OPERATORS

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
A query may fail with a -901 under the following conditions: 
1. There are multiple UNION operators at different level of 
query. 
2. One of the UNION operators has 3 or more duplicate branches, 
i.e. branches having exactly same set of tables, views, join and 
local predicates. 
 
An associated trap file may have below StackTrace: 
--- 
-------Frame------ ------Function + Offset------ 
0x09000000008CF470 pthread_kill + 0xB0 
0x09000000044A0F88 sqloDumpEDU + 0x74 
0x09000000044A1E4C sqldDumpContext__FP8sqeAgentiN42PCcPvT2 + 
0x11C 
0x09000000044A1C64 
sqldDumpContext__FP8sqeAgentiN42PCcPvT2@glueABB + 0x94 
0x09000000047D3E8C sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x350 
0x0900000003C7420C sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x24 
0x0900000003C73FB8 sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc + 
0x120 
0x0900000003C73CCC sqlnn_erds__FiN41e + 0x124 
0x0900000005148BB0 sqlnn_erds__FiN41e@glue611 + 0xB4 
0x09000000047EA08C 
prd_pulldown__9sqlnq_qunFPP9sqlnq_pidPFP9sqlnq_qncPiPP9sqlnq_pid 
T2_iPi 
+ 0xE8 
0x09000000060B056C sqlnr_sop_fix_hxp__FP9sqlnq_oprPiCP3loc + 
0x58C 
0x09000000060A77D4 sqlnr_optprep__FP9sqlnq_qur + 0x1040 
0x09000000060A66E4 
sqlnr_optprep_action__FP10sqlnr_qrwaPiP14sqlnr_progress + 0x10 
0x0900000004AE4BF0 
sqlnr_comp__FPiiP16sqlnr_rule_stateP10sqlnr_qrwaP14sqlnr_progres 
s@AF191_165 
+ 0x170 
0x0900000004AE2388 
sqlnr_comp__FPiiP16sqlnr_rule_stateP10sqlnr_qrwaP14sqlnr_progres 
s 
+ 0x44 
0x0900000004AE21AC 
sqlnr_seq__FPiP10sqlnr_qrwaP14sqlnr_progressP12sqlnr_rclass + 
0xBC 
0x09000000060F3740 sqlnr_rcc__FiP10sqlnr_qrwaPiP14sqlnr_progress 
+ 0x178 
0x0900000006508A5C sqlnr_exe__FP9sqlnq_qur + 0x10E4 
0x090000000652E69C sqlnr_exe__FP9sqlnq_qur@glue113A + 0x70 
0x09000000035ADC50 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_enviT7PP9sqlnq_qur 
+ 0x2294 
0x0900000003C63800 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_env 
+ 0x24 
0x0900000003C095C4 
sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P16sqlra 
_cached_varPiPUl 
+ 0x610 
0x0900000003C08240 
sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idUi 
T4PUcT4UsUcP14sqlra_cmpl_enviPiT11_T12_N311_T12_P14SQLP_LOCK_INF 
OPP16sqlra_cached_varT12_PUlb 
+ 0x404 
0x0900000003C07CAC sqlra_get_var__FP8sqlrr_cbiT2bPbT5 + 0x444 
0x09000000040B7728 
sqlrr_prepare__FP14db2UCinterfaceP16db2UCprepareInfo + 0x138 
0x0900000003B71FF8 
sqljs_ddm_prpsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0xAF0 
0x09000000036A2EB4 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface 
+ 0x10C 
0x0900000003D0ADE0 
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterface - 0x124 
0x0900000003D0C730 @63@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
+ 0x1D8 
0x0900000003E8A558 
@63@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0x98 
0x0900000003E8A3C8 
@63@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0xE0 
0x0900000003E8A13C sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0xD8 
0x0900000003E8BE00 RunEDU__8sqeAgentFv + 0x11C 
0x0900000003E96748 EDUDriver__9sqzEDUObjFv + 0x78 
0x0900000003E23550 sqloEDUEntry + 0x57C 
--- 
 
Db2diag.log may have below associated message: 
--- 
2011-04-25-13.57.43.493681+540 I13726A871         LEVEL: Severe 
PID     : 860292               TID  : 62836       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : DB2 
APPHDL  : 0-22222              APPID: 192.168.1.168.110425050011 
AUTHID  : DB2INST1 
EDUID   : 62836                EDUNAME: db2agent (DB050005) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:300 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 42 
 sqlerrmc: Pulldown attempted on a column with no hxp 
 sqlerrp : SQLNQ0A1 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFFF6      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
2011-04-25-13.57.43.505683+540 I14598A218         LEVEL: Severe 
PID:860292 TID:62836 NODE:000 Title: SQLCA 
Dump File:/home/db2inst1/db2dump/FODC_AppErr_.... 
---
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.7                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 5.                            * 
****************************************************************
Local-Fix:
Not available.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 UDB Version 9.7 FixPack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
16.05.2011
16.12.2011
16.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList