Re: On-Line headache
In article <1993May4.163749.22983@informix.com> davek@newjersey.informix.com (Dave Kosenko) writes:
>
>Charles Lei writes:
>|>
>|> SQL statement error number -240.
>|> Could not delete a row.
>|> SYSTEM error number -154.
>|> ISAM error: Deadlock Timeout Expired - Possible Deadlock.
>
>What I have to suspect you are experiencing is a "bug" (I quote it because
>I have not looked it up in our bug tracking system to verify that it has
>been designated a bug) that causes a lock timeout to return the error
>code for a distributed deadlock timeout. If you have any statements like:
> SET LOCK MODE TO WAIT 30
>(or any number), when that time expires, an error is returned to your app,>namely -154. What should be returned is a different error code
>indicating that the lock wait timeout has expired - it has NOTHING to do
>with deadlocks.
This is in fact a bug, but the "fix" will be simply to document -154 as being
EITHER a Deadlock Timeout or a Lock Wait Timeout. The theory being that
many customers will have already coded error handling for their applications
recognizing error -154 as Lock Wait Timeout, and that code should not break
when this bug is fixed.
June
#include <std.disclaimer>
-----------------------------------------------------------------
June Tong Informix Software, Inc.
Regency Support 4100 Bohannon Drive
(415) 926-6433 Menlo Park, CA 94025
e-mail: junet@informix.com or uunet!infmx!junet
-----------------------------------------------------------------