Hi All, I was told, my last message is not readable. Let me try to explain again:
If your active log is growing even if there was a TSM DB backup running - mostly started by the TSM server itself - check the timestamp of all logfiles. We had a similar situation where the server creates a new logfile every ten minutes. After opening a call at Tivoli Support, our solutions was: upgrade server to version 6.3.2.200. Hope that helps. best regards Ullrich Mänz Data Center Services FRITZ & MACZIOL Software und Computervertrieb GmbH Ludwig Str. 180D, 63067 Offenbach, Germany Mobil +49 170 7678 434 Fax: +49 69 3801 3500 10 Web: http://www.fum.de Amtsgericht Ulm, Handelsregister-Nummer: HRB 1936 Geschaeftsfuehrer: Heribert Fritz, Oliver Schallhorn Inhaber: Imtech N.V., Gouda, Niederlande Von: duholm <[email protected]> An: [email protected], Datum: 29.11.2012 09:06 Betreff: [ADSM-L] Active log Gesendet von: "ADSM: Dist Stor Manager" <[email protected]> Hi All My TSM server have trouble commiting the Active log to the database. At the moment I have an active log at 55 GB, so I had to cancel all my tasks running, and it has not stop the log from growing. So can anybody tell me, how I empty my Active log and what the normel bottlenecks are. My DB2 database and active logs are located on 7 200 GB SSD discs and I am running TSM ver 6.3.2.0. The CPU and RAM of the server are not used up nor are there any big disc queue lengths on any disc's. Hope somebody can help my Tanks Bo +---------------------------------------------------------------------- |This was sent by [email protected] via Backup Central. |Forward SPAM to [email protected]. +----------------------------------------------------------------------
