RE: sysproc* lock problems

Johnny, This sounds a lot like bug #22101. But, I had thought that it was fixed in version 5.02. Mention the bug number to tech support and perhaps they can give you an explanation. (FYI, back when we had this bug, it could only be fixed by upgrading.) --Craig (craig@chemistry.utah.edu) } }We are having problems with two processes concurrently executing the same }stored procedure. }The second process dies with locking errors, because the first process has }exclusive row locks }on sysprocplan and sysprocauth (I determined this by monitoring tbstat -k). }Why are all of }these locks necessary to simply execute a stored procedure? } } }Here are some additional facts: } }1. The stored procedure in question does call other stored procedures. } }2. Update statistics is not being run during this time. } }3. Online version is 5.05.UC1X3 running on NCR 35xx.