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 last weekend: Our recovery
log went full (but did not crash the server). The reason: Due to the
Daylight Savings Time (DST) error in the Windows TSM client, many of our
Windows clients did full backups after the DST switch. So, many backup
copies became inactive and were expired through the EXPIRE INVENTORY run
last weekend, causing an unusually big amount of change activity against
the DB, which all had to be buffered in the recovery log during DB
backup.

Reinhard


Wood, Dwight - BSC writes:
 > 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

--
Reinhard Mersch                        Westfaelische Wilhelms-Universitaet
Reinhard Mersch                        Westfaelische Wilhelms-Universitaet
Zentrum fuer Informationsverarbeitung - ehemals Universitaetsrechenzentrum
Roentgenstrasse 9-13, D-48149 Muenster, Germany      Tel: +49(251)83-31583
E-Mail: mersch AT uni-muenster DOT de                       Fax: 
+49(251)83-31653