Re: Illusive Locks

"Susan Elliott (ISG)" <SusanE@fclcis.co.nz> offerred: +Firstly, we tried to re-configure a table via the application (Baan) not +Informix. It comes up saying that there is an error 214. We tried +looking for a lock and could not find one. Rang Informix support, they +could not find the lock either.. and suggested that we bounce the +engine. Did that, and the lock went away (Funny that). The reconfigure +went through without a hitch. + +Since this occassion, we now use the following: +1) Bounce the engine, sometimes the entire machine +2) Select to reconfigure a table via the application that we use (Baan) +In theory every thing should be cool, 8 out of 10 times we are still +getting the error 214. + +So I'm now stuck for ideas !! +Has anyone else experienced "illusive locks" ??? +How did you eventually find them ???? +Has anyone any ideas of where I could look next ??? Why do you think there is a lock in the first place (and I think you mean "elusive" not "illusive")? Does the ISAM error indicate that the table is locked? The fact that you can't find a lock (did you run onstat? are you using online or SE?) indicates that a lock is not the root cause of the problem. You are aware of the fact that you cannot alter the structure of a table (which is what I assume you mean by "re-configure") as long as anyone else has that table open, whether or not they have any locks on it, yes? (there is a ucnt field in the tblspace structure that tracks how many users have that table opened; if the value for ucnt is > 1, the table structure cannot be altered). The isam error in this case is 106 (non exclusive access). Dave -- Dave Kosenko davek@summitdata.com Director of Training Services (732) 469-4070 Summit Data Group (an Informix Authorized Education Center)