| Cause Text: |
Multiple join classes are used when join queries are written that have
conflicting operations or cannot be implemented as a single query.
Each join class will be optimized and processed as a separate step
of the query with the results written out to a temporary table.
Access
plan implementation information for each of the join classes is not available
because access plans are not saved for the individual join class dials. Debug
messages detailing the implementation of each join dial can be found in the
joblog if the query is run in debug mode using the STRDBG CL
command. |