Re: SCO locking problem

Hi Yuri, I think you are not right. Only Online-DB has the option to set the lock mode (see: create table). On SE you only could get the page-lock problem if you have no primary key on your table. David has to check that there is everywhere an primary key. Perhaps his problems comes with changing database mode (ANSI/with or without transactions (START DATABASE)) !? cu Dirk Niemeier Yuri Dovgart schrieb: > In article <375658DB.E700ED1D@mail.telepac.pt>, > David Mendes <dmendes@fasoft.pt> wrote: > > Hi all, > > > > I had a system running SCO 3.4.2 with I-SE v.4.1. The system was > running > > for years with some 4GL programs. The system has a load of 2 or 3 > users > > on the program. > > We've updated the SE for 7.1. > > Now, when there is only one user everything works fine but when there > > are 2 or more it sometimes hans with the following error: > > > > SQL statement error number -263. > > Could not lock row for UPDATE. > > System error number -107. > > ISAM error: record is locked.> > > > It appears to be some kind of misconfiguration in the kernel (?), we > > have the row locking variable in the kernel set to a high value > > (FLCKREC=800) but it still has the problem ? > > > > Dear David. The problem is not in the OS type of locking. Problem is > that Informix uses page level locking by default. That means, that when > you need to update the row, all rows, placed on the page with needed > row, are locked. All you have to do is to change the type of locking > for your tables. You can do it in dbaccess in Table->Alter menu. Why > you have page level locking now ? Probably when you migrate from one > server to another, Informix creates all your tables with page level > locking, which is default. If you used dbschema utility for migration > you must enter -ss option to make schema with appropriate locking level. > Good luck ! > > -- > With best regards, Yuri Dovgart, > SAP R/3, Informix consultant, > "Telecominvest" company. > E-mail y_dovgart@tci.ukrtel.net > > Sent via Deja.com http://www.deja.com/ > Share what you know. Learn what you don't.