RE: LF usage

["Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>]

Deleted SM3UPD01 LF last night.
Weekly process ran this morning, no issues.
IBM query optimizer select another LF without issue.
Issue resolved.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Tuesday, May 24, 2016 8:45 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: LF usage

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>