Re: Long transaction

Joe Trubisz wrote: > > I think I have a problem, but I'm not sure. > I did an onstat -g ses and it said 'BLOCKED LONGTX' > I did an onstat -l and have over 50% free log files available. > > 1. Is this a critical problem? > 2. If so, what do I do about it? Check the $ONCONFIG file variables LTXHWM and LTXEHWM they are probably set at 50% and 60%. The engine detected a transaction spanning more than LTXHWM logspace and declared a LONG TRANSACTION condition which halts all other transactions than the long one and begins to roll that one back to free up log space for the others. When used log space exceeds LTXEHWM all open transactions are rolled back to free up log space. What to do? Obviously wait for the transactions to unwind and HOPE that you do not run out of free log pages before the rollback completes. For the future: 1) Increase number and/or size of logical logs. 2) Increase LTXHWM and LTXEHWM (not too much this is dangerous unless you also do 1). 3) Avoid long transactions! Do not hold locks especially in interactive applications. Use CURSOR WITH HOLD and COMMIT periodically in batch jobs to avoid long transactions and using up the lock table entries. Art S. Kagel