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 IC84015 Status: Geschlossen

EXP0009W ERROR IN EXFMT OUTPUT WHEN OPT GUIDELINE IS USED.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When DB2 registry variable DB2_OPTPROFILE is set to YES, for 
some 
queries when optimization guideline is used, EXP0009W may be 
returned in explain output and the optimization guideline will 
not be used. 
 
EX: 
 
select a.c1, b.c2, c.c1, d.c2, e.c1 
from tab1 a, tab2 b, tab3 c, tab4 d, tab5 e 
where a.c1=b.c1 and b.c1=c.c1 and c.c1=d.c1 and d.c2=e.c2 
/*<OPTGUIDELINES> 
           <HSJOIN> <ACCESS TABLE='e'/> <NLJOIN> <HSJOIN> 
<ACCESS TABLE='a'/> 
           <HSJOIN> <ACCESS TABLE='d'/> <ACCESS TABLE='b'/> 
</HSJOIN> 
           </HSJOIN> <ACCESS TABLE='c'/> </NLJOIN> </HSJOIN> 
           </OPTGUIDELINES>*/; 
 
 
The error in exfmt output: 
 
Extended Diagnostic Information: 
-------------------------------- 
 
Diagnostic Identifier:     1 
Diagnostic Details:     EXP0009W  Invalid access request. The 
table 
            reference identified by the TABLE attribute could 
            not be found. Line number "11", character number 
            "44".
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 fix pack 7                        * 
****************************************************************
Local-Fix:
As a temporary workaround, TABID can be used in the optimization 
guideline. 
 
EX: 
 
/*<OPTGUIDELINES> 
  <HSJOIN> <ACCESS TABLE='e'/> 
           <NLJOIN> 
                    <HSJOIN> <ACCESS TABID='Q1'/> 
                             <HSJOIN> <ACCESS TABID='Q4'/> 
                                      <ACCESS TABID='Q2'/> 
                             </HSJOIN> 
                    </HSJOIN> 
                    <ACCESS TABID='Q3'/> 
           </NLJOIN> 
  </HSJOIN> 
</OPTGUIDELINES>*/;
verfügbare FixPacks:
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
First fixed in DB2 version 9.7 fix pack 7
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
07.06.2012
31.12.2012
31.12.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP7
Problem behoben lt. FixList in der Version
9.7.0.7 FixList