× 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.


  1.  Home
  2. MIDRANGE-L
  3. April 2012

Re: SQL7917

On 26 Apr 2012 05:31, Mike Cunningham wrote:
SQL7917
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for
this statement, but the program could not be updated.

The additional text says the program may be locked. How does one go
about finding the cause of this? There is no reference to the object
that may be locked. This is occurring on an ODBC connection from a
linux box running a web app developed in PERL. (although I don't
think that matters). We see this in the QZDASOINIT job for the ODBC
connection

The term "program" is generic. The described scenario would likely be using a *SQLPKG object to store the access plan. Look at the P.S. [search on ps. in the document] to see some more comment at:

Subject: How to debug client server applications?
Date: Fri, 5 May 2000 12:41:35 -0400
http://archive.midrange.com/midrange-l/200005/msg00279.html
"ps. The problem turned out to be locks on the SQL package."

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.