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.
samir — — source: Informix-list mailing list archive (1991-1998)
Hi all,
WHen I try to have a lock on the table in exclusive mode there could still
be users accessing the table using ISOLATION DIRTY READ which does not
attempt to acquire a shared lock on a table or its records. So I am looking
how to track those users because I think that onstat don't do that.
Thanks for any suggestion
↪ replying to samir
Christian Brauer — — source: Informix-list mailing list archive (1991-1998)
> Hi all,
> WHen I try to have a lock on the table in exclusive mode there could still
> be users accessing the table using ISOLATION DIRTY READ which does not
> attempt to acquire a shared lock on a table or its records. So I am looking
> how to track those users because I think that onstat don't do that.
Maybe you could give the following select a try:
SELECT scs_sessionid, username
FROM sysmaster:informix.syssqlcurses,
sysmaster:informix.syssessions
WHERE scs_sessionid = sid
AND scs_sqlstatement MATCHES "*your_table_name*"
Bye, Chris
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.