Oninit cdi / Archive
Talk to an expert →

killing a process

Posted in 2001

Summary

Doug Fossmeyer had a hung Informix instance and asked how to kill active sessions. Andrew Hamm said to find the session id in onstat -u or onstat -g ses and run onmode -z sessionid as informix or root, not kill -9. The rollback may take a while; only afterwards use OS tools. Another poster also suggested onmode -z.

Auto-generated by Claude from the posts below — may be imperfect; read the full thread.

Topics: General Discussion

Doug Fossmeyer — — source: Informix-list mailing list archive (1991-1998)

I have a hung informix instance. Does anyone have any info on how to kill the active sessions? tia

↪ replying to Doug Fossmeyer
Andrew Hamm — — source: Informix-list mailing list archive (1991-1998)

Doug Fossmeyer wrote in message <94lc38$an0$1@news.xmission.com>... > >I have a hung informix instance. Does anyone have any info on how to kill >the active sessions? > Assuming you can identify the process in the onstat -u listing, you will see the session id there. Next, working as user informix or root (UNIX) or as a member of the informix-administrator (NT) issue onmode -z sessionid Don't try using kill from the UNIX command line. ESPECIALLY nasty kills like -9. If your hung session appears to be a server daemon process or a tape process or monitor process, call Informix support and tread carefully.

↪ replying to Andrew Hamm
Andrew Hamm — — source: Informix-list mailing list archive (1991-1998)

Andrew Hamm wrote in message <3a6e3899@news.iprimus.com.au>... > >Assuming you can identify the process in the onstat -u listing .... > But if you can't directly identify it, you need to work backwards from a ps listing. Get the process number, run onstat -g ses, identify the line with that process id (column 4) and get the session id from the first column. Then you are away.

↪ replying to Andrew Hamm
Andrew Hamm — — source: Informix-list mailing list archive (1991-1998)

Oops - final thought - it may take a while for the onmode -z to work. If the process has done a lot of work to get to where it is, then it may take a long time for the implied rollback to take effect. So don't panic if it doesn't disappear immediately. There will be flags in the onstat -u which will make it clear that the process is being kicked off by the engine. Once the process is gone as far as the engine is concerned, but if it's still hanging around in the O/S because of O/S problems, THEN you may start using more traditional UNIX techniques to get rid of it all together. But don't rush in here...

↪ replying to Doug Fossmeyer
cedarsiding@my-deja.com — — source: Informix-list mailing list archive (1991-1998)

Have you tried onmode -z <sessionid> ? -cs Sent via Deja.com http://www.deja.com/

Related threads