Long Transaction
Posted in 2007
Topics: General Discussion
Version: IDS 10
How can I track "tx" in following message: "Aborting Long Transaction:
tx 0xc0000001f4b64938". Is "0xc0000001f4b64938" the user address that
comes in onstat -u ? I am trying to track which process caused the
long transaction. I have a script that runs every 15 mts that captures
onstat -u, onstat -g ath and onstat -g ses. May be I need to increasethe frequency.
Execute:
$ onstat -a
and send
bye
<span style="color:rgb(0, 51, 102);font-weight:bold">The freedom of Linux
... The power of Informix</span>
>From: mohitanchlia@gmail.com
>To: informix-list@iiug.org
>Subject: Long Transaction
>Date: Sun, 30 Dec 2007 14:18:24 -0800 (PST)
>
>Version: IDS 10
>
>How can I track "tx" in following message: "Aborting Long Transaction:
>tx 0xc0000001f4b64938". Is "0xc0000001f4b64938" the user address that
>comes in onstat -u ? I am trying to track which process caused the
>long transaction. I have a script that runs every 15 mts that captures
>onstat -u, onstat -g ath and onstat -g ses. May be I need to increase>the frequency.
>_______________________________________________
>Informix-list mailing list
>Informix-list@iiug.org
>http://www.iiug.org/mailman/listinfo/informix-list
_________________________________________________________________
MSN Amor: busca tu ' naranja http://latam.msn.com/amor/
Hi,
0xc0000001f4b64938 is the address of the transaction you can get the transaction from :
onstat -x | grep c0000001f4b64938
The third column can be used to get the userthread:
onstat -u | grep <third column from onstat -x>
the third column here gives you the session ID
onstat -g ses <session ID> gives you all the information.
It is likely that by the time you run all this, the transaction will not exist anymore. So you can use the $INFORMIXDIR/etc/alarmprogram.sh to be notified by mail with all this information (Long transaction is event number 22).
Regards
gustavo
mohitanchlia@gmail.com wrote:
> Version: IDS 10
>
> How can I track "tx" in following message: "Aborting Long Transaction:
> tx 0xc0000001f4b64938". Is "0xc0000001f4b64938" the user address that
> comes in onstat -u ? I am trying to track which process caused the
> long transaction. I have a script that runs every 15 mts that captures
> onstat -u, onstat -g ath and onstat -g ses. May be I need to increase> the frequency.
> _______________________________________________
> Informix-list mailing list
> Informix-list@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list
>
>
>