ISAM error: Lock Timeout Expired
Posted in 2009
Topics: Error Codes & Troubleshooting, Connectivity: ESQL/C, 4GL & Embedded SQL
Can anybody let me know why we are getting the error below and how to resolve
this? Thx in advance.
ISAM error: Lock Timeout Expired
Date: 09/14/2009 Time: 16:53:30Program error at "fg_funcs.4gl", line number 1081.
SQL statement error number -243.
Could not position within a table (informix.stoohldd).
SYSTEM error number -154.
ISAM error: Lock Timeout Expired
Date: 09/14/2009 Time: 16:54:32Program error at "fg_funcs.4gl", line number 1081.
SQL statement error number -243.
Could not position within a table (informix.stoohldd).
SYSTEM error number -154.
ISAM error: Lock Timeout Expired
Date: 09/14/2009 Time: 16:55:15Program error at "fg_funcs.4gl", line number 1081.
SQL statement error number -243.
Could not position within a table (informix.stoohldd).
SYSTEM error number -154.
ISAM error: Lock Timeout Expired
Your application is using a SET LOCK MODE TO WAIT <n seconds>; command to
avoid lockout errors from transient locks, however, some poorly written
application (probably a new one recently rolled into production) is holding
locks for longer than the wait timeout setting.
Finderr tells the story, especially the explanation for the ISAM error
(-154):
$ finderr 243 154-243 Could not position within a table table-name.
The database server cannot set the file position to a particular row
within the file that represents a table. Check the accompanying ISAM
error code for more information. A hardware error might have occurred,
or the table or index might have been corrupted (truncated). Unless the
ISAM error code or an operating-system message points to another cause,run the oncheck utility (secheck with IBM Informix SE or tbcheck with
IBM Informix OnLine) to check and repair table and index.
-154 ISAM error: Lock Timeout Expired.
This network operation has been suspended, awaiting a response from
another database server, for the maximum duration allowed. The local
database server assumes that a distributed deadlock exists and that
this user request is awaiting a resource that was locked by a user in a
different system, which is awaiting a resource that this user owns.
Roll back the current transaction, and retry it after a delay. If this
error occurs frequently, ask the database server administrator to adjust
the length of the deadlock time-out interval.
This code is also returned when an explicit wait time limit expires;
that is, if you have SET LOCK MODE TO WAIT 3, and your request is
queued for more than 3 seconds for a lock, the operation ends with this
ISAM error code.
Art
Art S. Kagel
Oninit (www.oninit.com)
IIUG Board of Directors (art@iiug.org)
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Oninit, the IIUG, nor any other organization
with which I am associated either explicitly or implicitly. Neither do
those opinions reflect those of other individuals affiliated with any entity
with which I am affiliated nor those of the entities themselves.
On Mon, Sep 14, 2009 at 6:54 PM, DEEPAK JOSHI <djoshih@hotmail.com> wrote:
> Can anybody let me know why we are getting the error below and how to
> resolve
> this? Thx in advance.
>
> ISAM error: Lock Timeout Expired
> Date: 09/14/2009 Time: 16:53:30> Program error at "fg_funcs.4gl", line number 1081.
> SQL statement error number -243.
> Could not position within a table (informix.stoohldd).
> SYSTEM error number -154.
> ISAM error: Lock Timeout Expired
> Date: 09/14/2009 Time: 16:54:32> Program error at "fg_funcs.4gl", line number 1081.
> SQL statement error number -243.
> Could not position within a table (informix.stoohldd).
> SYSTEM error number -154.
> ISAM error: Lock Timeout Expired
> Date: 09/14/2009 Time: 16:55:15> Program error at "fg_funcs.4gl", line number 1081.
> SQL statement error number -243.
> Could not position within a table (informix.stoohldd).
> SYSTEM error number -154.
> ISAM error: Lock Timeout Expired>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--0023545bdb809d7343047394baca