Re: What happens if logical logs are full

> ber@knapp.knapp.at (Erwin Burgstaller) wrote: > > >Maybe a former question was to complex. Now I'm asking only: > > >Is it possible to recover from full logical logs, with almost no loss of > >data? > > Hi Erwin, > > It depends on whether the logs were filled due to a long transaction > that spanned all logs, or you just have not backed up your logs. > In the second case all you need to do is go to screen and back up the > logs. In the first case it basically restore from archive. If anyone > out there knows a another way to recover from a long transaction that > fills log I would love to hear from you. If it IS due to a long transaction, you should do the following to avoid a recurrence: (1) Change your high water mark parameters (LTXHWM and LTXEHWM) to below 50 (%). That way OnLine will always have enough room to roll back any long transactions. (2) Prevention is better than cure: track down the code that caused the long transaction, slap the author, and change it to use much shorter transaction durations. Avoid spanning waits for user input if you can. (3) If you really are running with much too few logs, increase the size and number One other way the logs can clog up is if the log it's trying to go to next contains the most recent checkpoint record. The solution here is simply to force a checkpoint. Have a look at tbstat -l to see what's actually going on. akent@cix.compulink.co.uk (Andy Kent) ------------------------------------------------ Freelance Informix Database Specialist, Redland, Bristol, England