Re: tables locked

From: hash100@mail.eclipse.net (Atiq Hashmi) > >I have some triggers on some tables. I am trying to delete them, >I deleted some but for others it complains that the underlying >table of that trigger is locked by another user. This is what I >get for a trigger defined on table10: > ># 242: Could not open database table (Kim.table10). ># 106: ISAM error: non-exclusive access. > >I looked at my informix server host and 'onstat -g ses' does not >show that Kim owns any session. We normally use isql for any database >work and I don't see any process indicating that Kim has left any >isql or database access process running. > >I am getting this error message for many tables and I don't think that >Kim was working on all tables at one time. And... the Kim is on vacation. >I want to solve the prob. without reboot online to clear up locks. > > >Questions: >1. Is there a way to tell who has locks on a table. The syslocks > table doesn't have this info ?. >2. Is there a way to clear the locks held by another user ?. >3. Will rebooting Kim's workstation help ? (assuming Kim only > was accessing the informix from her workstation only). >4. I sometimes get this error even though I am not accessing the > table. Sometimes just getting out of isql completely helps, sometimes > not. What should be done in that case. ? Well, the error message you're getting doesn't say that Kim holds the lock, only that she created the tables. :-) 1. Use onstat -k to see who's holding locks. 2. Kill the process that's holding the locks. 3. No. 4. It's just that whoever was locking the table dropped the lock while you were recycling your isql session. Look into row level locking. HTH. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com