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