Re: Why this Long Transaction?

In article <jlumbleyCKH6Hy.19r@netcom.com> jlumbley@netcom.com (Joe Lumbley) writes: >Folks, > >I've run across something I'm not sure about and thought maybe the >accumulated nettelligence could figure it out. > >Twelve hours ago my large database was shut down ungracefully, with >a monster insert operation going on. About 2 million rows in the table, >but I don't know how many were actually inserted. On restart, we went into >that misnomer of all misnomers , "fast recovery". That was about 11.5 >hours ago. It's been recovering since then. > >At about the 10.5 hour mark, my tbstat -t output showed a Long Transaction >flag. My LTXHWM is 70% and my LTXEHWM is 80%. I'm currently at about 40% >log usage and nothing else is running. So why the long transaction? Are >there different rules for how the HWM's work in recovery? Is there some >kind of time check? I know it won't make any difference and I'll still be >recovering for another 45 minutes, but it's bothering my little monkey brain. > Good question. Rollbacks can cause a long transaction to occur, but according to your parameters, it shouldn't happen until 14 logs are full. What kind of machine are you running on that the rollback takes that long? Whenever we've seen a rollback that long, it never came out of recovery and we had to call support to set aside recovery with a tbzero. Did yours finally come out? ----------------------------------------------------------------- Jim Burks jburks@promus.com The Promus Companies Memphis, Tennessee, USA