Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Arvind Sharma got error -244 with ISAM error -113 selecting from a mostly read-only table and asked how to release the lock. Art S. Kagel said Informix locks cannot outlive their owner: run onstat -k to find the table's partnum with an exclusive lock, match the owner in onstat -u, then use onstat -g ses with the session id. Robert Taylor suggested SET ISOLATION TO DIRTY READ. No outcome was reported.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Arvind Sharma — — source: Informix-list mailing list archive (1991-1998)
Hi,
When I am doing a select on a table it is giving me error -244 and
ISAM error -113. These errors say that the table is locked and it cannot do a physical read on that table. Is there a way by which we can
release the lock? I don't think any body has a put a lock on that table
as it is mainly used for read purpose only. Please let me know if there
can be any other problem.
P.S. Please reply to my email id too.
Thanks
Arvind
↪ replying to Arvind Sharma
Art S. Kagel — — source: Informix-list mailing list archive (1991-1998)
Arvind Sharma wrote:
>
> Hi,
> When I am doing a select on a table it is giving me error -244 and
> ISAM error -113. These errors say that the table is locked and it can> not do a physical read on that table. Is there a way by which we can
> release the lock? I don't think any body has a put a lock on that table
> as it is mainly used for read purpose only. Please let me know if there
> can be any other problem.
Note that the fact of this message disagrees with your assessment that
noone has a lock on the table. Unless you are using the SE engine, you
did not post version and platform information you bad boy, Informix
automatically manages locks and it is not possible for a lock to
outlive it's owner.
Run onstat -k and look for the table's partnum in hex in the tblsnum
column with a rowid of 0 and type X or HDR+X for exclusive lock. Then
run onstat -u and grep for the value in the owner column. The third
column of that output is the session id of the session that has the
lock outstanding. Run onstat -g ses <session id> to see what process
that is, who is running it, and what it is doing at the moment.
Art S. Kagel
↪ replying to Arvind Sharma
Robert Taylor — — source: Informix-list mailing list archive (1991-1998)
Before you read do
SET ISOLATION TO DIRTY READ
Arvind Sharma <asharma@uswest.com> wrote in message
news:3784C7E3.95F496E4@uswest.com...
> Hi,
> When I am doing a select on a table it is giving me error -244 and
> ISAM error -113. These errors say that the table is locked and it can> not do a physical read on that table. Is there a way by which we can
> release the lock? I don't think any body has a put a lock on that table
> as it is mainly used for read purpose only. Please let me know if there
> can be any other problem.
>
> P.S. Please reply to my email id too.
>
> Thanks
> Arvind
>
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.