Re.: Online Problems

lei@mtcdev.MEDIATECH.COM (Charles Lei) wrote > Order Entry application kept bombing out with the following group of > messages: > > SQL statement error number -240. > Could not delete a row. > SYSTEM error number -154. > ISAM error: Deadlock Timeout Expired - Possible Deadlock.> > SQL statement error number -244. > Could not do a physical-order read to fetch next row. > SYSTEM error number -154. > ISAM error: Deadlock Timeout Expired - Possible Deadlock.> > Is this a manifestation of the infamous twin paradox problem? We've > increased the deadlock time out from 60 seconds to 300 seconds, but > this error kept occurring. You have not mentioned the kind of transactions you are using, but it is quite possible that, with more than one user on the system the transactions enter a deadlock. At least the database engine thinks that there is a possibility of a deadlock and enters a timeout phase. This problem would not arise in SE since, maybe, you did not use transactions. In my experience, increasing the timeout will not necessarily break the deadlock. In one of our applications, we got around this problem by trapping the status values of -244 and -240 and setting our own wait mechanism. That worked great, since we did not abort any transactions. Hope this helps, Atul. -- --------------------------------------------------------------------------------Atul Patankar | "There is always one more bug" email: apatanka@magnus.acs.ohio-state.edu | "My bug is bigger than yours" Phone (W): (614) 575 6652 | All Disclaimers apply.