IDS Forum

Re: Advise needed

Posted By: Marco Greco
Date: Monday, 9 November 2009, at 2:33 p.m.

In Response To: Advise needed (DEEPAK JOSHI)

DEEPAK JOSHI wrote:
> Hi All,
>
> Our users are bouncing back to the main 4gl application window
> while entering orders and due to this they are losing orders.
>
> I can see that below errors on 4gl application logs but no errors on Informix
> DB 7.13 running on Hp-UNIX 10.01.
>
> Please guide me how to troubleshoot this and the best approach to resolve this
> issue & where could be the problem on application side or a database side.
>
> Errors on 4GL application logs
>
> ISAM error: Lock Timeout Expired
> Date: 11/06/2009 Time: 15:31:03
> Program error at "bl_peggr.4gl", line number 1043.
> SQL statement error number -245.
> Could not position within a file via an index.
> SYSTEM error number -154.
> ISAM error: Lock Timeout Expired
> Date: 11/06/2009 Time: 15:41:33
> Program error at "bl_dtl.4gl", line number 99.
> SQL statement error number -245.
> Could not position within a file via an index.
> SYSTEM error number -154.
> ISAM error: Lock Timeout Expired
> Date: 11/06/2009 Time: 15:52:27
> Program error at "bl_peggr.4gl", line number 1043.
> SQL statement error number -245.
> Could not position within a file via an index.
> SYSTEM error number -154.
> ISAM error: Lock Timeout Expired
> Date: 11/09/2009 Time: 13:32:01
> Program error at "bl_peggr.4gl", line number 1043.
> SQL statement error number -245.
> Could not position within a file via an index.
> SYSTEM error number -154.
> ISAM error: Lock Timeout Expired
> Date: 11/09/2009 Time: 13:34:50
> Program error at "bl_peggr.4gl", line number 1043.
> SQL statement error number -245.
> Could not position within a file via an index.
> SYSTEM error number -154.
> ISAM error: Lock Timeout Expired
> .......so on
>
> continous same error
>
> We are observng this error for the couple of days and now it start effecting
> the users work. please help.
>
> Regards
> Deepak
>

Deepak - the issue is that there's a client application that's holding a lock
on a resource and not releasing it, while another client application (the one
that throws the error) would like to use it and has given up waiting for it.
The causes could be many - from a client that has started a transaction,
locked a row, and just went away for lunch (rather long lunch, two days),
though hopefully you should see it becoming long at some stage, and rollback,
to your instance generally becoming slower (maybe you lack required indexes,
or table hold more data than developers have anticipated), and client
applications now release locks in a longer time frame that your developers
have coded.
Without seeing the application logic or the instance, I can't really tell you
more.

Note though that this is the kind of error that a half decent developer would
have trapped and handled inside the application, so by all means nag your
developer and have it fixed by him, if he is still around, that is.

As a side and personal note - you should start paying a bit more attention to
what people tell you around here: ODS 7.13 is out of support, HPUX 10.01 is
out of support, your 4gl is most likely out of support, and you really should
be looking to enroll into some informix courses....
--
Ciao,
Marco
______________________________________________________________________________
Marco Greco /UK /IBM Standard disclaimers apply!

Structured Query Scripting Language http://www.4glworks.com/sqsl.htm
4glworks http://www.4glworks.com
Informix on Linux http://www.4glworks.com/ifmxlinux.htm

Messages In This Thread

• Advise needed
  DEEPAK JOSHI -- Monday, 9 November 2009, at 2:20 p.m.
  • Re: Advise needed
    Marco Greco -- Monday, 9 November 2009, at 2:33 p.m.
  • Re: Advise needed
    Eric Rowell -- Monday, 9 November 2009, at 2:49 p.m.
  • Re: Advise needed
    Art Kagel -- Monday, 9 November 2009, at 2:51 p.m.
  • Re: Advise needed
    Andrew Clarke -- Monday, 9 November 2009, at 6:51 p.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.