To prevent it happening again:

-put the workaround in your dsmserv.opt:
  ALLOWREORGTABLE NO

-On Windows, the physical size of the log can grow significantly larger
than what you specify with the ACTIVELOGSIZE parm.
I've learned to keep a dummy 2G file on the drive with the activelog.
That way if the log goes nuts and eats up all the drive space, I can get
the server restarted just by removing the file, without having to grow
the LUN.  (Although I've had no such problem since re-implementing
ALLOWREORGTABLE NO).

W 


 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Dave Canan
Sent: Wednesday, April 07, 2010 4:31 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM 6.1.3 WIndows no log space how to restart
server

See if the following helps. What you need to do is get a db backup done
so
that logs are then cleared.

http://www-01.ibm.com/support/docview.wss?uid=swg21394424


Dave Canan
IBM TSM Advanced Technical Support
TSM Performance
ddcanan AT us.ibm.com


On Wed, Apr 7, 2010 at 11:32 AM, Nicholas Rodolfich <
NRodolfich AT cmaontheweb DOT com> wrote:

> Hello All,
>
>
> I have a client with a new TSM 6.1.3 server on Windows 2008. It
crashed
> earlier because it is out of log space. How can I bring the sever back
up.
>
>
>
> Regards,
>
> Nicholas
>