|
Problem IC62675
|
Status: Closed |
SQL0901 REASON "SQLNO_CRULE_JOIN [350]" RETURNED WHEN OPTIMIZATION GUIDELINE WITH FIRST ATTRIBUTE IS USED |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Compiling a query with an optimization guideline that includes a
join request with the FIRST attribute may result in the
following error:
SQL0901N The SQL statement failed because of a non-severe
system error.
Subsequent SQL statements can be processed. (Reason
"sqlno_crule_join [350]:rc( 0) ".)
SQLSTATE=58004
Here is an example of such an optimization guideline:
<OPTGUIDELINES>
<NLJOIN FIRST="TRUE">
<ACCESS TABLE="TABLE1"/>
<ACCESS TABID="Q10"/>
</NLJOIN>
</OPTGUIDELINES>
This can happen if no valid query plan can be generated using
the guideline. Under normal circumstances, if a guideline
cannot be used, the optimizer should ignore the guideline and
generate a valid plan. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* Compiling a query with an optimization guideline that *
* includes a *
* join request with the FIRST attribute may result in the *
* *
* following error: *
* *
* *
* *
* SQL0901N The SQL statement failed because of a *
* non-severe *
* system error. *
* *
* Subsequent SQL statements can be processed. (Reason *
* *
* "sqlno_crule_join [350]:rc( 0) ".) *
* *
* SQLSTATE=58004 *
* *
* *
* *
* *
* *
* Here is an example of such an optimization guideline: *
* *
* *
* *
* <OPTGUIDELINES> *
* *
* <NLJOIN FIRST="TRUE"> *
* *
* <ACCESS TABLE="TABLE1"/> *
* *
* <ACCESS TABID="Q10"/> *
* *
* </NLJOIN> *
* *
* </OPTGUIDELINES> *
* *
* *
* *
* This can happen if no valid query plan can be generated *
* using *
* the guideline. Under normal circumstances, if a guideline *
* *
* cannot be used, the optimizer should ignore the guideline *
* and *
* generate a valid plan. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.7 fix pack 1. *
* *
* Alternatively, correct the optimization guideline so it can *
* be used to generate a valid query plan or disable *
* optimization guidelines for the query. *
**************************************************************** |
| Local Fix: |
Correct the optimization guideline so it can be used to generate
a valid query plan. Alternatively, disable optimization
guidelines for the query. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows
|
| Solution |
Fixed in DB2 version 9.7 fix pack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.08.2009
17.02.2010
17.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
