Re: Let me be the first

Lukas Barton wrote: > I mean I'm facing the problem described on: > > http://www-1.ibm.com/support/docview.wss?rs=0&context=SSGU5D&context=SSHMMC&context=SSGU8G&context=SSGKNY&context=SSGU5Y&context=SSCRW7&context=SSGHZP&context=SSVT2J&q1=ISAM+error%3a+record+is+locked.&uid=swg21152738&loc=en_US&cs=utf-8&lang= > > 244: Could not do a physical-order read to fetch next row, 107: ISAM > error: record is lock> > The number of rows in the table is small enough to cause the database > server to perform a sequential scan, and an index scan on a table > with lock mode configured to row. Having gone through your test case with IDS 10.00.UC5 I agree you probably are since you can only select the rows without encountering a lock if OPTCOMPIND is set to 0 and the locking mode is row. So why not set OPTCOMPIND to 0 in your ONCONFIG and solve the problem? If you're in an OLTP environment it's highly desirable anyway and in a mixed environment it probably won't hurt. It's also highly desirable to set LOCK WAIT to something other than zero. Ben.