Re: Update stat/sysprocplan

Update statistics will not remove the lock, it creates one. Update statistics on a database that never sleeps creates a verydifficult problem because of the exclusive locks it places on files AND on some of the system catalogs. I don't know what else could place a lock like this on a sysprocplan. A CREATE PROCEDURE should only lock records in sysprocplan, but could it be locking more than it should? pfinkel@cbnews.cb.att.com (paul.d.finkel) wrote: >We've had a problem where the sysprocplan table has an exclusive lock >placed on it. This only occurs when one procedure is run. I am investigating >and testing the procedure now. >Question: when I asked Informix tech support about this problem, they suggested >that running "UPDATE STATISTICS PROCEDURE <procedure name>" had resolved a >customer's problem. According to TFM that command "updates the optimized >execution plans for procedures in the sysprocplan system catalog table". >Will running the UPDATE remove the lock on that table? >I'm willing to try it, but I'd like to know what I'm doing. >Any thoughts or suggestions? >-- > ---------------------------------------------------------------- > Do unto others ... then split! > MaryAnne Stasium > ----------------------------------------------------------------