|
Problem IC84015
|
Status: Closed |
EXP0009W ERROR IN EXFMT OUTPUT WHEN OPT GUIDELINE IS USED. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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>*/; |
| available fix packs: |
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
|
| Solution |
First fixed in DB2 version 9.7 fix pack 7 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.06.2012
31.12.2012
31.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP7
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.7
|
 |
