Author: "Wood, Dwight - BSC" <DWood2 AT CHW DOT EDU>
Date: Wed, 6 Dec 2000 08:49:33 -0700
My recovery log filled up and crashed the server this morning. I have the recovery log in "Normal" mode - NOT "Roll Forward" mode. I was under the impression that the recovery log would not fill up a
Author: Lawrence Clark <Larry_Clark AT THRUWAY.STATE.NY DOT US>
Date: Wed, 6 Dec 2000 11:07:25 -0500
It fills until the db reaches a 'sync' point. Something like a number of clients backing up concurrently but not as yet completed can fill up the log file. My recovery log filled up and crashed the s
Author: Palmadesso Jack <Jack.Palmadesso AT SWPC.SIEMENS DOT COM>
Date: Wed, 6 Dec 2000 11:16:45 -0500
You may want to expand the size of your recovery log. That would at least reduce the chances of crashing due to a full recovery log. The logs will usually fill up if you have alot of sessions going a
Author: Wood, Dwight - BSC [mailto:DWood2 AT CHW DOT EDU]
Date: Sun, 04 Oct 2015 17:25:42 -0500
My recovery log filled up and crashed the server this morning. I have the recovery log in "Normal" mode - NOT "Roll Forward" mode. I was under the impression that the recovery log would not fill up a
Author: John Naylor <John.Naylor AT SCOTTISH-SOUTHERN.CO DOT UK>
Date: Wed, 6 Dec 2000 16:30:02 +0000
Well, You have 2 possibles either :- 1) Your log is not big enough for you workload. Do you monitor/trend its max utilization 2) You have a rogue session or process that caused the problem. If you st
Lots of uncommitted transactions. I've seen this before on logs around a gig in size. You wouldn't think the works would/could get that far behind, but with large transaction loads it happens. Kelly
Author: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Date: Sun, 04 Oct 2015 17:25:42 -0500
My recovery log filled up and crashed the server this morning. I have the recovery log in "Normal" mode - NOT "Roll Forward" mode. I was under the impression that the recovery log would not fill up a
Author: Reinhard Mersch <mersch AT UNI-MUENSTER DOT DE>
Date: Thu, 7 Dec 2000 08:47:38 +0100
Hi, contrary to the other responses you got so far, I would think that 1.5 GB log size should be big enough for a 13.5 GB DB if you are doing daily DB backups. (Ours is 0.8 GB , Db size ist 38 GB.) W