Re: Locks Limits ... Informix 7.22

Rick asks: >Is there a mechanism to automatically "kill" an Informix ODS task >which is acquiring too many locks? We encountered a situation this >morning where a programmer was deleting the contents of several >tables and failed to issue "commit work" statements. As a result, >his task acquired almost a million locks and prevented other tasks >from proceeding. > >I am accustomed to another (mainframe) database where limits >can be established on such system-wide resources. Does Informix have >such a feature? Or is it necessary to run a UNIX script which periodically >issues onstat commands and reviews the resources held by each task? > >How do other shops prevent similar problems? There is no such limit built into the current releases. In a shop where I worked, we built special "deletion programs" to purge old data from tables. We went so far as to issue BEGIN and COMMIT statements after *each row* in order to avoid any possible problem with locking or logging. Then it's a matter of training your people to use them, and to not issue system-wrecking SQL statements. This problem is broader even than locks. See the archives for posts on how to limit table and database creation statements by users. Sorry we don't have a that kind of function. (Yet?) ___________________________________________________________ Clem Akins (aka clem@informix.com) <- NEW ACCOUNT! Informix Software, Inc (Standard disclaimers apply) International Technical Support Last seen: Attending the IIUG Board meeting, Menlo Park