Re: High Water Mark Question

Here's some more info on the situation - the transaction in question was an unwise delete (another issue altogether) of every row in a very large table. Logs are > 300MBytes, plenty of space. They were probably close to needing to be backed up at the time the long txn started. This was the only activity of any substance on the system at the time. The academic question at this point is: Why did the database "hang" when there should have been plenty of ability to roll back? That's why the LTX parms Possibilities as I see it: 1. The system wasn't really "hung up" at all, it was just rolling back exclusively (refusing to do any other work) for a long time and misinterpreted that way. 2. Some aspect of rolling back deleted rows takes an enormous amount of space (Logging is buffered, so wasted llog space is minimal...) 3. Outright engine bug. Greg Bill Ennis wrote: > snip.... > > > > Hi > > > > Our database was hung recently due to a long transaction. Our LTXHWM = 20 and > > LTXHWM = 30 , which are pretty low. I am not sure why the database couldn't > > rollback and recover from this long transaction. Anyone has any idea ? > > > > Thanks. > > Keith > > > > -- > Bill Ennis Voice: 312-474-7516 > SSA Fax: 312-474-7460 > 500 W. Madison email: ennis@ssax.com ennis@accesschicago.net