RE: ISAM Error -154

Have you checked what kind of ISOLATION LEVEL are you applying and what is the lock level you are using? , Suppose you have isolation level REPETABLE READ or CURSOR STABILITY this kind of isolation level=20 places a lock, even more REPETABLE READ places locks on all the rows it reads even if the row does not match actually your where clause, and would be worst in SCAN READS., so you may start by checking both the lock level and the ISOLATION LEVEL. I hope this helps, ---------------------------------------------------------------- Mario Estrada / SISTECO, S.A. INFORMIX, / Phone (502) 3340214 Support Department / Fax (502) 3348447 ---------------------------------------------------------------- W.Agnes wrote the following: ---------- De: W. Agnes Leung[SMTP:agnes@alumnae.caltech.edu] Enviado: s=E1bado 18 de enero de 1997 19:35 Para: informix-list@rmy.emory.edu Asunto: ISAM Error -154 We're running Informix 7.1, everything runs fine in one site. However, when we have our program (actually a daemon) running on several sites, we're getting SQL error -243 (sometimes -244, depends on whether it is a SELECT or FETCH statement) with ISAM error -154 under = the following condition: 1). The remote site is down and bring back up, say, for maintenance 2). Trying to access the LOCAL database will then get the error 3). We have to kill and restart the program (daemon) at ALL sites The Informix documentation states error -154 has something to do with distribute deadlock ..... by why does it happen only when a remote site is bounced, and only when accessing the LOCAL database ? The error occurs on SELECT, FETCH as well as UPDATE and INSERT = statements. Our Informix database is running on Sun Solaris, over TCP/IP ATM = network. We're located in California and our remote sites are located in Florida = as well as Paris. Anyone has any idea what's going on ? =20