Re: Killing off client thread

Cheryl, Thanks for the help! The problem, unfortunately, is not something that I can handle just in the client - my client connects to a server which does the actual OCBC call. It is that server that doesn't release the connection properly. Of course, now that i've made the devel team aware they screwed up, they'll fix it, but meanwhile I'll have to kill the idle threads by hand. *sigh* Anca. The command is onmode -z <pid>,where pid is the Unix Process ID/Session Id for the User Transation you want to stop. I noticed that you mentioned that the problem only occurs when your client program crashes. Have you coded for a ROLLBACK (discard all changes thus far in transation) or COMMIT {keep transations changes thus far in this transaction) when an ERROR occurs? This should release all locks held by the transaction. ------------------------------------------------------------------------- Cheryl Kendricks Internet:cherylk@prod1.jcdc.doleta.gov OR cherylk@gwysmtp.jcdc.doleta.gov DTSI, Inc. Database Administrator - DOL Job Corps San Marcos, Texas