Re: Informix and isolation modes

On Fri, 27 Jun 1997 mserafino@ameritrade.com wrote: > We have an application that runs with the isolation set to committed read. Is this the same program with the memory problems you mentioned earlier? > Sometimes the application locks up when we enter dbaccess and do selects Just doublechecking -- does it lock up at any other time? You say sometimes.. what is the pattern / common-thread in the lockup situations -- only after its been running for a while for instance? > against a table the application uses. This is very infrequent but can > occur even when we set our isolation mode to dirty read while in dbaccess. The access mode of the dbaccess SQL shouldn't make any difference. > Are their any Informix Guru's who can restore :-) my faith in Informix by > helping with the following questions? Well, we can try... before we start, though, it would be useful if you'd let us know your compiler and engine version numbers, along with your platform and O/S level. > 1) Have you ever heard of anything like this before? No, not really. Sorry. > 2) Do readers affect writers in Informix??? (yuck) Well, I /am/ responding to your post ... oh, you mean the Online Engine. No, they certainly shouldn't (barring disk i/o delays, et cetera). Even repeatable read doesn't care if others are looking at rows, especially when they use dirty read themselves. > 3) What are we doing wrong? Maybe if you give us some more information -- what is the program doing when it locks up? Does it lock up indefinately, or momentarily? What is the program's SET LOCK MODE statement set to? If it errors out, what are the SQL and ISAM error codes? > 4) If the answers to 1,2,3 are yes, yes, and nothing then is SQL Server > any good or is it just a toy? :-) segmentation violation: unreferenced question > thanks for the help! > Mike Serafino Come back with some more specifics, and we'll do our best to help fix your little problem. -Richard