RE: Transaction Rollback
Nice idea, but when the server goes into exclusive mode no access is
possible
Regards
Colin
>From: "David Buchholz" <David.Buchholz@VITALPS.COM>
>To: "Colin Dawson" <cjd_1955@hotmail.com>, <informix-list@iiug.org>
>Subject: RE: Transaction Rollback
>Date: Tue, 26 Apr 2005 06:56:44 -0700
>
>Colin,
>
> Yep. Try this query in sysmaster:
>
>set isolation to dirty read;>
>select logbeg, loguniq, logpos
>from systxptab
>where indx = <value> {If you know the exact transaction number}
>where longtx <> 0 {If the engine is rolling back a long tx}>
> If you run this repeatedly, you'll see the logpos rapidly (or slowly
>depending on your stress level) decreasing and when it reaches zero,
>loguniq will decrement until it reaches logbeg and you're done. You can
>basically time how long it takes to rollback through one log and multiply
>that time by how many you have to go. Works for us.
>
>-Dave
>------------------------------------
>Vital Processing Services
>David Buchholz
>Sr. Database Administrator
>David.Buchholz@VITALPS.COM
>------------------------------------
>
>
>-----Original Message-----
>From: owner-informix-list@iiug.org
>[mailto:owner-informix-list@iiug.org]On Behalf Of Colin Dawson
>Sent: Tuesday, April 26, 2005 01:06
>To: informix-list@iiug.org
>Subject: Transaction Rollback
>
>
>Hi All,
>
>
>Is there a way to monitor a long transaction rollback and how much work it
>has left to do?
>
>
>
>Regards
>
>Colin
>
>
>sending to informix-list
>
>
>sending to informix-list
sending to informix-list