Re: SYSPROCPLAN locked using Stored Procedures

Sysprocplan will become locked anytime a stored procedure needs to be = recompiled. This can happen if someone has released a stored procedure to live, or a = database change has gone to live which affects a stored procedure. I don=27t know whether the poster is treating Sp changes as database = changes but they should be. We take a full application outage here to release SPs. rgds Peter Tashkoff <tashkop=40iname.com> Zespri International Limited Std Disclaimers Apply All rights reserved. No party may use this document to vilify another. Zespri New Zealand Kiwifruit, The World=27s Finest >>> David Williams <djw=40smooth1.demon.co.uk> 15/11/97 07:50:04 >>> In article <19971114172201.MAA27613=40ladder02.news.aol.com>, DRSantee <drsantee=40aol.com> writes >We are using 16 bit PowerBuilder 5.02 connecting through its native = driver > using I-Net 5.01.WJ2 executing a stored procedure on Informix Online = 5.06.UC2. > Occassionally (we can not reproduce at will or with any consistency = yet) the > SYSPROCPLAN table becomes locked and gives a second user an SQL -211 = error.=20 > There was a bug in Online where locks were held on sysprocplan. Upgrade to the latest version (I run 5.08 and I think later versions=20 are available). >Danny Santee >City of Aurora >Aurora, Co >dsantee=40ci.aurora.co.us=20 --=20 David Williams