Re: LF usage -- MIDRANGE-L

Subject: Re: LF usage
From: CRPence <crpbottle@xxxxxxxxx>
Date: Tue, 24 May 2016 07:44:54 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 24-May-2016 07:21 -0500, Steinmetz, Paul wrote:

<<SNIP>> IBM query optimizer is being used to determine which access
path should be used for updates. Our LF being selected instead of
vendors STMTM3L0. Deleting our LF, SM3UPD01, will resolve the issue.
<<SNIP>>

I suppose so. Quite difficult for the last-used info to get updated for an object that no longer exists :-) Hardly seems a /resolution/ however:

<sarcasm> Damned optimizer choosing to implement with /the wrong/ keyed access path. Nothing like a good use of [an effective] DROP INDEX to /teach a lesson/ to that query optimizer ;-) The optimizer should stop finding that AccPth and start creating plans to find the data [rows to be changed] using a less-optimal\efficient path! </sarcasm>

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: LF usage , Steinmetz, Paul

This mailing list archive is Copyright 1997-2025 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.