Re: Informix 5 / dbspaces / Help!

James Walsh Jr. <jew@tpghq.com> wrote in article <01bbe95c$67396ba0$e7462399@cianci>... > I'm working on a systems integration project using Informix 5 and am having > some peculiar errors crop up in a database. There are two different > databases running, being used by two different applications. The problem > can be localized to a single database and application, but I"m at a loss on > how to fix it. > > I'm getting the error back that reads 'Unable able to perform physical read > to fetch next row'. The vendor of the application seems to think that the > dbspace is too small, and should be created on another physical segment. I > haven't been able to find out if 1. This is possible, and 2. If this will > even solve the problem. You usuaully get another error code back along with the one that says "Unable to perform physical read to get the next row" that should give you a clue as to why. The most common reason I have seen is that the row or page is locked. I doubt this would have anything to do with the size of the dbspace. If the problem DOES turn out to be locking, then you can use "onstat -k" to list the locks. You will then have to do some other "onstat"s to find the exact lock which is causing you problems and tie that lock to a specific process. In any case, your application may need some tweaking to prevent it from holding locks for too long, and/or you may need to "set lock mode wait". (Be careful with changing the lock mode though -- see the manual for cautions.) Setting the table locking granularity to "row" from "page" may help also. HTH -- Irwin Goldstein Objective Software Systems, Inc. http://www.objectsoft.com