Re: HELP ME WITH THE FAQ....Please review

mweallans@panacea.co.uk wrote: > David, > I'm qute willing to help with "What exactly is a long transaction" but > it needs a complete rewrite. It currently recommends using "onarchive" > and I'm not sure if that is still distributed. I don't even know if > informix would recommend clearing a long transaction in that way. It > also doesn't take any account of newer advances with dynamic allocation > of logs etc. I agree. I am not sure I would follow any of the advice in this section of the FAQ although it's probably not all bad. If a transaction has become "long" it has essentially failed but it has left the database engine in a state where no-one else can perform any transactions since the next logical log is not available. My solution would be to add another logical log somewhere to the system, preferably in the chunk containing my other logical logs (I would leave space for this eventuality) and roll back the long transaction. Of course there is dynamic allocation of logs now as you say so this may not even be required on newer systems. If you absolutely have to run the transaction and can't rewrite it then you either need more logical logs or you need to perform the transaction with logging turned off. This last option brings up a whole host of other issues with backups, rolling back, inability to use transactions at all, HDR etc. Ben.