RE: Long Transaction Abort !!

Within the message log you should be able to see the LTX abort message, this will give at least a session id and maybe a user. From the session you can trace you they are and hence what they are doing. One of the common application errors causing this is the following logic begin work do things to tables wait for user input commit work To avoid it happening you can increase the log space, but if it is a logic problem then this will only lengthen the time it takes to trigger - it will not solve the problem Paul Watson # WF Software Ltd # If it ain't broke Tel: +44 1463 674729 # Fix it until it is Fax: +44 1463 678729 # www.wfsoftware.com # > -----Original Message----- > From: StudJaggu [mailto:sujaggu@yahoo.com] > Sent: 27 April 1999 14:18 > 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 >