RE: Potential Long transactions

Haven't looked at this thoroughly yet, but thought that I'd point out that
you can get $ONCONFIG values (like LTXHWM) directly out of sysmaster.

select * from sysmaster:sysconfig where cf_name like 'LTX%'

cheers
j.

Sane ego te vocavi. Forsitan capedictum tuum desit.

-----Original Message-----
From: informix-list-bounces@xxxxxxxx
[mailto:informix-list-bounces@xxxxxxxx]On Behalf Of Mohit
Sent: Monday, February 25, 2008 8:07 PM
To: informix-list@xxxxxxxx
Subject: Potential Long transactions


Version: IDS 10

I have written below query to find out those transactions that could
be potential long transactions. Assuming 50/60 is high water mark
values:

select s.txid,r.owner, r.sid, scb.pid
from systxptab s, sysrstcb r, sysscblst scb
where (loguniq-logbeg)/(select sh_maxlogs
from sysshmvals) > 40/100 { catch when it's
over 40% }
and logbeg > 0 { I saw lot of transactions owned by informix that
have logbeg as 0 }
and s.owner = r.address
and r.sid = scb.sid;

Does this query look correct ? I didn't know how to get LTXHWM value
from sysmaster to hard coded the values. Any suggestion or
improvement ?
_______________________________________________
Informix-list mailing list
Informix-list@xxxxxxxx
http://www.iiug.org/mailman/listinfo/informix-list

.

Relevant Pages

  • Re: Potential Long transactions
    ... you can get $ONCONFIG values (like LTXHWM) directly out of sysmaster. ... I have written below query to find out those transactions that could ... have logbeg as 0} ...
    (comp.databases.informix)
  • RE: Potential Long transactions
    ... The only point I would add is that the query assumes that sh_maxlogs ... Subject: Potential Long transactions ... you can get $ONCONFIG values directly out of sysmaster. ... have logbeg as 0} ...
    (comp.databases.informix)