Re: SQL7917 Access plan not updated -- 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 DBMON trace showed me that the objects in question were stored
procedures in our general purpose library, accessed from different
environments.
And that's not good implemented by us of course, because it will try to
update access plans from different libraries in the same program object.
So we will have to do some code rewrites on this issue.

Regards,
-Arco

2016-12-20 14:52 GMT+01:00 Rob Berendt <rob@xxxxxxxxx>:

I sent in a DBMON trace just last week. Still waiting on development to
read it.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: Arco Simonse <arco400@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/20/2016 08:42 AM
Subject: Re: SQL7917 Access plan not updated
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

IBM sent me a reference:

Message SQL7917 at R610 and Higher Releases
http://www-01.ibm.com/support/docview.wss?uid=nas8N1010982

And the advice to send in a DBMON trace.

Regards,
-Arco

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.