Lock error on trigger creation

I'm getting the following error when I try to create a trigger (My angle brackets): 242: Could not open database table (<tablename>). 106: ISAM error: non-exclusive access. Whatever is causing the block has been there all morning. As far as I can tell by querying syslocks and grepping onstat -k with hex(partnum), neither <tablename>, nor the table the trigger accesses, nor systriggers have any locks on them. Where to next? Interestingly SET LOCK MODE TO WAIT makes no difference either. The error comes back immediately. What gives? Andy

"Andy Kent" <andykent.bristol@virgin.net> wrote in message news:a3525a11.0401160429.34836a06@posting.google.com... > I'm getting the following error when I try to create a trigger (My > angle brackets): > > 242: Could not open database table (<tablename>). > 106: ISAM error: non-exclusive access. Is there an open cursor on the table? When a trigger is created on a table, the structure of the table is deemed modified, in the sense that any application having an open cursor on it will get error -710.

andykent.bristol@virgin.net (Andy Kent) wrote in message news:<a3525a11.0401160429.34836a06@posting.google.com>... > I'm getting the following error when I try to create a trigger (My > angle brackets): > > 242: Could not open database table (<tablename>). > 106: ISAM error: non-exclusive access.> > Whatever is causing the block has been there all morning. > > As far as I can tell by querying syslocks and grepping onstat -k with > hex(partnum), neither <tablename>, nor the table the trigger accesses, > nor systriggers have any locks on them. > > Where to next? > > Interestingly SET LOCK MODE TO WAIT makes no difference either. The > error comes back immediately. What gives? > > Andy The table is opened. do onstat -g opn and use the partnum in hex of the table to find out by whom. It gives you the thread id ( tid ).