RE: Long Transaction Abort !!

Steps to find a long running transaction. 1) onstat -x This will tell you the userthread which has the longest transaction (the earliest log begin entry) 2) onstat -u to find the session id with that user thread 3) onstat -g ses <sesid> to find pid and user and whatever sql statement this session is doing. The biggest culprit I can think of for causing a long transaction is a lock being held while waiting for user input. The best solution would be do not allow that ... Will Rice P.S. There might be a better way to do this with systables, but I dont run into this, so haven't had to figure something like that out... -----Original Message----- From: StudJaggu [SMTP:sujaggu@yahoo.com] Sent: Tuesday, April 27, 1999 8:18 AM To: informix-list@iiug.org Subject: Long Transaction Abort !! Hi , Can somebody, please, reply on the following problem : we have a financial transaction processing system. recently during the day, sometimes our system becomes very slow. we traced the reason. during these points of extreme slowness -- the informix log has generally a long transaction abort message. we are trying to find out "which of our programs cause this long txn abort?" my queries are : 1) can someone give some tips on how to pinpoint the exact queries/insert/update stmts which are causing long txn abort? 2) what are the ways by which we could avoid long txn abort (eg. say by increasing the logical logs or by changing some informix parameters.) 3) what care should be taken while coding such that the code doesn't cause such long txns? thanks in advance, sandeep -- Such is life and such is growing And thru' mistakes, we end up in knowing !!! -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own