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.
I'm trying to find a way how to monitor when a
long transaction is almost going to happen on an
informix instance. We are using the IDS version
7.24. Can this be done using onstat utilities or
via an sql query on the sysmaster database.
With an onstat -l you can see the logical logs
which have been backed up but you can't see if
there is a long running transaction busy with
onstat -l. Logical logs will recycle but arethan reaching the LTXHWM or LTXEHWM values.
Can somebody help me to find a way of monitoring
this? Thanks.
Sent via Deja.com http://www.deja.com/
Before you buy.
↪ replying to jphilips@my-deja.com
Art S. Kagel — — source: Informix-list mailing list archive (1991-1998)
jphilips@my-deja.com wrote:
>
> I'm trying to find a way how to monitor when a
> long transaction is almost going to happen on an
> informix instance. We are using the IDS version
> 7.24. Can this be done using onstat utilities or
> via an sql query on the sysmaster database.
>
> With an onstat -l you can see the logical logs
> which have been backed up but you can't see if
> there is a long running transaction busy with
> onstat -l. Logical logs will recycle but are> than reaching the LTXHWM or LTXEHWM values.
>
> Can somebody help me to find a way of monitoring
> this? Thanks.
You can use onstat -x to monitor transactions. One of the columns is
the unique logid of the first log containing records for that transaction.
If the physical log number of that uniqid is near recycling (or near the
LTXHWM threshhold actually, then you are approaching a long transaction.
You can also monitor the sysmaster:systxptab which contains the same info
plus the uniqid of the latest log containing records for that transaction
which will allow you to distinquish between large transactions and stalled
ones (ie someone went out to lunch holding a lock. This can help you
track down offending applications and redesign them.
Art S. Kagel
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.