SCO locking problem
Hi all,
I had a system running SCO 3.4.2 with I-SE v.4.1. The system was running
for years with some 4GL programs. The system has a load of 2 or 3 users
on the program.
We've updated the SE for 7.1.
Now, when there is only one user everything works fine but when there
are 2 or more it sometimes hans with the following error:
SQL statement error number -263.
Could not lock row for UPDATE.
System error number -107.
ISAM error: record is locked.
It appears to be some kind of misconfiguration in the kernel (?), we
have the row locking variable in the kernel set to a high value
(FLCKREC=800) but it still has the problem ?
What is happening ?
Please help me !
David Mendes
David Mendes wrote:
> Hi all,
>
> I had a system running SCO 3.4.2 with I-SE v.4.1. The system was running
> for years with some 4GL programs. The system has a load of 2 or 3 users
> on the program.
> We've updated the SE for 7.1.
> Now, when there is only one user everything works fine but when there
> are 2 or more it sometimes hans with the following error:
>
> SQL statement error number -263.
> Could not lock row for UPDATE.
> System error number -107.
> ISAM error: record is locked.
This is a programming issue. Only one user can update a record at a time.
More than likely is that after the update, the record(s) were not released
or unlocked. The old version just let you get away with this.
>
>
> It appears to be some kind of misconfiguration in the kernel (?), we
> have the row locking variable in the kernel set to a high value
> (FLCKREC=800) but it still has the problem ?
>
> What is happening ?
> Please help me !
>
> David Mendes
David Mendes wrote:
>
> Hi all,
>
> I had a system running SCO 3.4.2 with I-SE v.4.1. The system was running
> for years with some 4GL programs. The system has a load of 2 or 3 users
> on the program.
> We've updated the SE for 7.1.
> Now, when there is only one user everything works fine but when there
> are 2 or more it sometimes hans with the following error:
>
> SQL statement error number -263.
> Could not lock row for UPDATE.
> System error number -107.
> ISAM error: record is locked.>
> It appears to be some kind of misconfiguration in the kernel (?), we
> have the row locking variable in the kernel set to a high value
> (FLCKREC=800) but it still has the problem ?
Just add SET LOCK MODE TO WAIT 10; to your 4GL programs and they will
wait for the lock to clear for 10 seconds before receiving a lock
error. If the problem still occurs there may be a design problem with
your applications. I do not know why you did not see this behavior
before.
Art S. Kagel