Re: logical logging

Thuc Nguyen <thucn@inconnect.com> wrote: >When I changed to /dev/null on the primary drive from /dev/ifmx/1m and >then turned off the B logging, then I ran the sql script after long >transaction aborted. Once the script was done, I turned the logging back >on and changed to /dev/ifmx/1m. My understanding is that the logical log >- completed will be lost that are not backed up. If that is correct, how >I restore the logical log? Is it too late? If you turned logging off, there's a gap in the logical logs anyway. If you need to restore, you'll have to use a level-0 archive (presumably you were forced to take one in order to get logging turned on again). >What is the best way to do that without turning off the B logging to >run a sql script? Increase your logical logs so that the log transaction high water mark isn't reached. Alternatively, you can increase the long transaction high water mark values (LTXHWM/LTXEHWM) in the onconfig. Hope this helps. Regards, John Morton mortonj@interlog.com