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) 531-5926
Fax: (719) 260-5991
Email: [EMAIL PROTECTED]
www.storsol.com
www.storserver.com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Wood, Dwight - BSC
Sent: Wednesday, December 06, 2000 8:50 AM
To: [EMAIL PROTECTED]
Subject: Recovery Log Problems while in Normal Mode
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 and crash the system
while in normal mode. The log is 1.5 GB and the DB is 13.5 GB. We do a full
DB backup once a day, sometimes twice. When I restarted the server the log
showed up as 0.1% utilized. Does anyone have any idea as to what might cause
the log to fill up? I am running TSM 3.7.3 on Solaris. Thanks,
-Dwight
