Re: Why does 5.04 lock up when logs fill?

Tom, Why can't you just add more logs? Or if that's not an option, lower the tbconfig parameters LTXHWM and LTXEHWM. If they're still 80 and 90, which was the default in version 5.X, then you must lower them to something like 40 and 50. This will ensure that a long transaction will have enough log space to rollback, thereby preventing the logs filling and the need for a restore. If your user still needs to do that big transaction, then buy a disk and increase the number and size of the logical logs. It's a straight forward procedure which can be done while the system is online (although it does require a level 0 backup to be run after you've added the new logs.) But in any case, check what those parameters are set to. They make quite a difference. Hope this helps, Tracy > > 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. > > tom. > -- ========================================================================= = Tracy W. Nedd = = Banctec Inc. - DBA = = Silver Spring, Md = = tracyn@banctec.clark.net or tracyn@asd.banctec.com = ========================================================================= = ALL RIGHTS RESERVED. = = This posting is copyright and may be used only for the purposes = = of professional study, or the professional exchange of information. = = Use of this posting by any commercial organization for the purposes = = of vilifying another is explicitly prohibited. = =========================================================================