Re: Orphaned sql turbo processes.

Christopher Cale Internet: chrisc@spamis.jcdc.eta.gov Systems Administrator Voice: 1-800-598-5008 Metrica, Inc. 205 6th St. San Marcos, Tx USA 78666-9007 On 26 Sep 1994, Danni Bauer wrote: } Brian A. Lind (snicker@netcom.com) wrote: } > In article <pduttaCw9xvu.8y5@netcom.com>, } > Partha Dutta <pdutta@netcom.com> wrote: } > >Jonathan Leffler (johnl@informix.com) wrote: } > >: >From: shyam@minerva.robadome.com (Shyam Davuburu) } } > Stuff deleted... } } > While we're on the subject... } > At my current job all the programmers were told to never, ever kill } > a sqlturbo process, but to get the DBA to do it. I, of course, totally } > ignore this policy when I need to bail out of a long querey. I use kill -15. } > > Yea, I had a programmer that had the same attitude...He constantly } > > killed sqlturbo processes and it never screwed anything up....until } > > one day it brought the engine down in the middle of the day...oops. } > There seems to be some concern that if you are doing an update to the } > Informix database and you do a kill -15 on the process, that sqlturbo } > will not clean up any locks. I always assumed it was smart enough to clean } > up after itself as long as you didn't do a kill -9. } > Does anyone out there confer or am I off base? } > We use Informix 4.11 on the Pyramid. } > Thanks. } } Never kill the sqlturbo process. You can kill the front-end process (isql, etc.) } with the software termination signal (15). IT will take care of stopping the } back-end process (sqlturbo). If you need to stop the sqlturbo process because } it's orphaned use: } } tbmode -z {pid} } } This usually takes a while (minutes is not unusual). } } -- } -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- } } __ Danni Bauer } / )_ ' bauer@gtetel.com } /(_/(//)/)/ 73764.63@compuserve.com }