Re: Why does 5.04 lock up when logs fill?

tom dorgan wrote: > > I guess the subject says it all. the server just quits and you have to > restore the database? This is what our admin people are doing, anyway > and its a 6 hour process and all you get is what you had on your last > backup. Doesnt seem like the last word in data safety/reliability. > > somebody does a transaction which affects quite a few rows of the > database, the logs fill, and everything comes to a very quiet halt. It sounds as though they are generating a long transaction. This should never occur if OnLine is tuned correctly. Take a look at the parameters: LTXHWM Long transaction high-water mark LTXEHWM Long transaction high-water mark exclusive These are 80% and 90% respectivly by default, although in 7.something they default to 50% and 60%. The first says how big a transaction will get before it is automatically declared LONG and rolled back. The second says how much log space is used before the rollback of a long transaction 'hogs' the remaining space. If this remaining space is filled by the rollback, then OnLine will lock! It cannot free the logs because the transaction is active, and it cannot rollback the transaction because there is no log space. If these are okay, then look at increasing the number of logs with LOGFILES. If this length of transaction MUST occur, then you will have to do this anyway. Hope that helps, -- Mark. +-------------------------------------------------------------------------+ |Mark D. Stock - The West Solutions Group http://www.west.co.za | | The Informix FAQ is at http://www.iiug.org | |mailto:marks@west.co.za +------------------------------------------------+ |Tel: +27 11 803 2151 |If it doesn't work... force it! | |Fax: +27 11 803 2189 |If it breaks... it needed replacing anyway! | |Cell: +27 83 250 2325 |Well, that's how I code anyway! | +------------------------+------------------------------------------------+