This problem has been reported on the list many times; it tends to be worse in some versions of TSM than others. What platform/version are you running? And how big is your log?.
And as Josh said, it is more likely to happen when there are multiple DB-intensive tasks running together. Also more likely to happen when in roll-forward mode. One of the TSM servers here finally grew so busy I could not run expiration without filling the log, which was already max size (5 GB), had to go back to NORMAL mode instead of roll-forward. -----Original Message----- From: Joshua S. Bassi [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 18, 2001 12:11 PM To: [EMAIL PROTECTED] Subject: Re: recovery log is filling up so quickly I typically *try* and backed up the TSM DB while no other processes are running. Of course this doesn't always occur, especially when I am designing TSM solutions around products like TDP for SAP which dump transaction logs randomly throughout the day. -- Joshua S. Bassi Independent IT Consultant IBM Certified - AIX/HACMP, SAN, Shark Tivoli Certified Consultant- ADSM/TSM Cell (408)&(831) 332-4006 [EMAIL PROTECTED] -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Pothula S Paparao Sent: Thursday, October 18, 2001 1:31 AM To: [EMAIL PROTECTED] Subject: recovery log is filling up so quickly Importance: High Hi floks, Strange problem. Recovery log fills up rapidly and causes server to crash. This only seems to occur when DB2 backup happening. I tried backing up Db2 database parellel with 4 session 8 buffers, but of no use. I also tried increasing the log , didnt click. any suggestions.
