SYSTEM error number -107
I am new with informix IDS and trying to solve following problem:
Server OS : Solaris 2.6
Informix IDS : Informix Dynamic Server Version 7.30.UC7
INFORMIX-4GL Version 7.20.UD6
Problem
Application running slow and always get following error log :
Date: 08/09/2008 Time: 11:11:35
Program error at "discaj.4gl", line number 1072.
SQL statement error number -244.
Could not do a physical-order read to fetch next row.
SYSTEM error number -107.
ISAM error: record is locked.
Date: 08/09/2008 Time: 11:12:29Program error at "bil97.4gl", line number 3316.
SQL statement error number -244.
Could not do a physical-order read to fetch next row.
SYSTEM error number -107.
ISAM error: record is locked.
Date: 08/09/2008 Time: 11:12:34Program error at "bil97.4gl", line number 3316.
SQL statement error number -244.
Could not do a physical-order read to fetch next row.
SYSTEM error number -107.
ISAM error: record is locked.
Date: 08/09/2008 Time: 11:14:41Program error at "bil97.4gl", line number 3316.
SQL statement error number -244.
Could not do a physical-order read to fetch next row.
SYSTEM error number -107.
ISAM error: record is locked.
Date: 08/09/2008 Time: 11:26:36Program error at "bil97.4gl", line number 3316.
SQL statement error number -244.
Could not do a physical-order read to fetch next row.
SYSTEM error number -107.
ISAM error: record is locked.
Date: 08/09/2008 Time: 11:27:47Program error at "bil97.4gl", line number 3316.
SQL statement error number -244.
Could not do a physical-order read to fetch next row.
SYSTEM error number -107.
ISAM error: record is locked.
Date: 08/09/2008 Time: 11:28:56Program error at "bil97.4gl", line number 3316.
SQL statement error number -244.
Could not do a physical-order read to fetch next row.
SYSTEM error number -107.
ISAM error: record is locked.
Date: 08/09/2008 Time: 11:31:59Program error at "bil97.4gl", line number 3316.
SQL statement error number -244.
Could not do a physical-order read to fetch next row.
SYSTEM error number -107.
ISAM error: record is locked.
Can someone help me where to check please
thanks
This is line 3316 bil97.4gl
-
-
-
update daftar set daftar.hutang = gr_daftar.hutang,
daftar.kod_disc = gr_daftar.kod_disc,
daftar.dt_disc = gr_daftar.dt_disc,
daftar.tm_disc = gr_daftar.tm_disc
where daftar.rn = gr_daftar.rn
If SQLCA.SQLCODE < 0 Then
return
Else
# Audit Trail
let kod_fungsi = "BIL<B>"
let task = "UPD"
let table = "DAFTAR"
let rn_rst = gr_daftar.rn
let var_rnrst = "gr_daftar.rn"
-
-
-
This application running without problem before
Go into the source code of ALL of your programs that access the Informxi
databases and immediately after the CONNECT or DATABASE statement (or at the
top of MAIN in a 4GL program that has a DATABASE statement ONLY outside of
MAIN - ie at the top of the file) insert the following SQL statement:
SET LOCK MODE TO WAIT 10;
Your users are blocking each other out of scanning data rows because they
are encountering each others' transient locks. This is the immediate fix.
You do, however, have at least one larger problem. The ISAM level error was
-107, "record is locked", which the SQL line above will alleviate, however,
the SQL level error was -244, "Could not do a physical-order read to fetch
next row" which indicates that the queries that were so locked out were
performing sequential scans of the data tables, NOT using indexes (otherwise
the SQL error would have been different). Either there are indexes missing
from your database or your data distributions are out-of-date and you need
to UPDATE STATISTICS. See the instructions for correctly doing this in the
Informix Performance Guide (your version of IDS is so old that John Miller's
paper on improved algorithms for doing this do not apply).
You should SERIOUSLY consider upgrading your IDS engine. There have been at
least five levels of performance improvement in the Informix database engine
since 7.30 plus many new features!
Art
On Sun, Sep 7, 2008 at 11:59 PM, MUMIN MARJUKI <mumin@akapost.com> wrote:
> I am new with informix IDS and trying to solve following problem:
>
> Server OS : Solaris 2.6
> Informix IDS : Informix Dynamic Server Version 7.30.UC7
> INFORMIX-4GL Version 7.20.UD6
>
> Problem
>
> Application running slow and always get following error log :
>
> Date: 08/09/2008 Time: 11:11:35
> Program error at "discaj.4gl", line number 1072.
> SQL statement error number -244.
> Could not do a physical-order read to fetch next row.
> SYSTEM error number -107.
> ISAM error: record is locked.
> Date: 08/09/2008 Time: 11:12:29> Program error at "bil97.4gl", line number 3316.
> SQL statement error number -244.
> Could not do a physical-order read to fetch next row.
> SYSTEM error number -107.
> ISAM error: record is locked.
> Date: 08/09/2008 Time: 11:12:34> Program error at "bil97.4gl", line number 3316.
> SQL statement error number -244.
> Could not do a physical-order read to fetch next row.
> SYSTEM error number -107.
> ISAM error: record is locked.
> Date: 08/09/2008 Time: 11:14:41> Program error at "bil97.4gl", line number 3316.
> SQL statement error number -244.
> Could not do a physical-order read to fetch next row.
> SYSTEM error number -107.
> ISAM error: record is locked.
> Date: 08/09/2008 Time: 11:26:36> Program error at "bil97.4gl", line number 3316.
> SQL statement error number -244.
> Could not do a physical-order read to fetch next row.
> SYSTEM error number -107.
> ISAM error: record is locked.
> Date: 08/09/2008 Time: 11:27:47> Program error at "bil97.4gl", line number 3316.
> SQL statement error number -244.
> Could not do a physical-order read to fetch next row.
> SYSTEM error number -107.
> ISAM error: record is locked.
> Date: 08/09/2008 Time: 11:28:56> Program error at "bil97.4gl", line number 3316.
> SQL statement error number -244.
> Could not do a physical-order read to fetch next row.
> SYSTEM error number -107.
> ISAM error: record is locked.
> Date: 08/09/2008 Time: 11:31:59> Program error at "bil97.4gl", line number 3316.
> SQL statement error number -244.
> Could not do a physical-order read to fetch next row.
> SYSTEM error number -107.
> ISAM error: record is locked.>
> Can someone help me where to check please
>
> thanks
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
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.
Running OK before and now having lock problems points directly to out dated
data distributions. Definitely need to UPDATE STATISTICS, as I recommended
in my previous reply to your previous post.
Art
On Mon, Sep 8, 2008 at 12:08 AM, MUMIN MARJUKI <mumin@akapost.com> wrote:
> This is line 3316 bil97.4gl
> -
> -
> -
>
> update daftar set daftar.hutang = gr_daftar.hutang,>
> daftar.kod_disc = gr_daftar.kod_disc,
>
> daftar.dt_disc = gr_daftar.dt_disc,
>
> daftar.tm_disc = gr_daftar.tm_disc
>
> where daftar.rn = gr_daftar.rn
>
> If SQLCA.SQLCODE < 0 Then
>
> return
>
> Else
>
> # Audit Trail
>
> let kod_fungsi = "BIL<B>"
>
> let task = "UPD"
>
> let table = "DAFTAR"
>
> let rn_rst = gr_daftar.rn
>
> let var_rnrst = "gr_daftar.rn"
> -
> -
> -
>
> This application running without problem before
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
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.