Re: lock problem

I have also this lock problem but the only way I can do is shutdown and restart the Informix Engine. Here is the case: I want to export a database. I'm successful to do the update statistic on the database. There no activities on the database. I check it with 'onstat -g sql' or 'onstat -g ses'. But I still get the database refused to the dbexport with lock error message. I check if there are some synonym that can cause this problem but no synonym were created on this database. It's very strange problem for me and I saw it twice. The informix engine is IDS 7.30.UC2 on UW7.0.1 H.V Art S. Kagel <kagel@bloomberg.net> wrote in message news:38188F74.5E3D02B7@bloomberg.net... > "Sackwitz, Antje" wrote: > > > > Hi, > > coming from the Oracle world I focus a problem in my informix database. > > In a table with a lot of concurrent activities on that table (insert , > > update, select) > > and having a lot of rows the select very often runs into a lock and > > therefore can't proceed the select. > > How can I configure that reading the data is still possible or that the > > concerned row is omitted, and select proceeds with the next row? > > Any help is greatly appreciated. > > If you need a consistent picture of the data use: > > SET LOCK MODE TO WAIT; { Wait for locks to clear forever }> -or- > SET LOCK MODE TO WAIT 10; { Wait for locks to clear for 10 secs }> > Otherwise, use: > > SET ISOLATION DIRTY READ;> > Art S. Kagel