Re: Non Exclusive Access Error

Jeff Larsen wrote: > Why am I getting the following error when onstat -k shows no locks > other than the usual session locks on sysdatabasees. > > 242 Could not open database table (owner.tabname), > 106: ISAM error: non-exclusive access.> > Shouldn't the shared lock that is preventing exclusive access > show up in onstat -k? > > What's the deal? > > Jeff Larsen > larsen@qec.com Non-exclusive access is not restricted to just locks. If someone has the table open for any reason (dirty read even), then you can't get exclusive access. You should be able to get the partnum of the table from systables, then look for that partnum in an onstat -t or -T output. The onstat -[t|T] output should have a column name of ucnt. The is the user count, so if the table has a ucnt > 1( the 1 including the person trying to do whatever needs exclusive access) then you don't have exclusive access. -- ******************************************************************** * Jacques P. Renaut "I'd dazzle you with brilliance * * Informix Advanced Support if I only had the knack..." * * email: jrenaut@informix.com #include <disclamier.h> * ********************************************************************