Re: Too many locks

Mike Shatila a 'crit dans l'article <33df7d73.180672264@nntp>... >On Tue, 29 Jul 1997 16:25:46 +0100, while dropping acid Grzegorz Fus ><gfus@daewoo.com.pl> spewed: > >How many locks do you have defined in the $ONCONFIG file. > That's not the problem here, what ever the value defined, the requester wanted to know a way to cancel a transaction holding all locks on the server. He explicitly stated that he had a bug in one of its queries, so all locks were unexpectedly allocated. I suppose that the problem he has is that he cannot stop the query in failure, because without any lock, you cannot either connect to the server. This issue has been solved in 7.2 apparently, because you can always at least shut down and restart the server in fast recovery mode (so that the failing transaction is rolled back appropriately). Did he try to shut down ? If it does not work, at least it should be able to kill the Informix server process, then release the shared memory block (using the "ipcs" command to list it, and "ipcrm" to remove it from root), before restarting in slow recovery mode. in 7.2, you should always be able to do at least a "ontape -s" to backup the transactions prior to killing the server, and you should always be able to force a checkpoint after that, so that killing the server will not loose any information.