Re: Query Optimizer selection incorrect access path -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

The OP should use Visual Explain to see just what is happening - it would tell them which engine is in use. And a whole bunch of other information, very useful stuff.

It might be helpful for us to see more detail - DSPFD of the SO logical, original table, the actual statement - have we seen those yet from the OP?

But if they think it's a bug, it's time to call IBM again.

HTH
Vern

On 11/5/2012 4:01 PM, CRPence wrote:

On 05 Nov 2012 13:59, Charles Wilt wrote:

The only reason the QE would use a select/omit logical is that it
was specified in the query or when IGNORE_DERIVED_INDEX=*NO and
the select/omit criteria matched the WHERE clause of the query.

That QAQQINI Query Option Parameter, whether or not to ignore Derived
Indexes, applies only to SQE processing. Thus another possibility
explaining the choice of the derived access path, is that the query is
being processed by the CQE. Any query implemented via the CQE could use
any S\O LF over the data, irrespective of the value\specification for
that INI option. My reply does not intend to imply any relevance for
the query described by the OP.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.