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.)
Was EXPIRE INVENTORY running when the server crashed?
Perhaps you had the same problem as we had
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 J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949-1313
(719) 53
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 at once.
Or especially if you use the Lotus Notes 4.6 agent. Its my understanding
that some data
<[EMAIL PROTECTED]> on 12/06/2000 04:07:25 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject: Re: Recovery Log Problems while in Normal Mode
It fills until the db reaches a 'sync' p
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.
>>> [EMAIL PROTECTED] 12/06/00 10:49AM >>>
My recovery log filled up and crashed the server this morning. I have the
recovery log in "Normal
