Re: URGENT - System Crash

Yup. You're hosed. Do yourself a favor and set LTXHWM and LTXEHWM to nice low numbers. I have mine set to 20 and 30, logs are nice & spacious though. In my case, if someone is doing a single transaction bigger than 20% of 300ish megabytes, I want to know about it so I can go slap their hands. Rolling the transaction back pretty much guarantees I hear about it real quick. Keeps me from shooting myself in the foot too, which I've done a few times. BTW, with v7 engines, I've gone through Onmonitor and shut the engine down in mid transaction to stop a runaway, then on restart it rolls back the interrupted transaction. Crude but effective in a pinch. Beats a Level 0 restore up & down the block. Probably should work for v5 as well. As for applying the latest logical logs, if you did, you would just end up right back where you were, with a royally hosed system. V7.2 and above does point in time recovery via onbar, or I guess you could apply the logs, and then shutdown & restart the engine once that nastly LTXN gets underway. Yuck. Greg Nigel Gall wrote: > > Hi y'all! > > OK. I'm in the process of restoring form last night's backup. While doing > the restore, I was prompted whether I would like to save the logical logs > on disk to tape, to which I replied Yes, thinking that I would be able to > restore any closed/commited transactions within the logs when the > rollforward begins. > > But one of you said that I should NOT restore from these logs that were > present when the system crashed. Can you all explain why exactly? > snip....