Hana, you may want to take a look at the following URL. This is the
procedure that support will walk you through if you are not familiar with
DB2 backups and restore. If you have questions, I encourage you to call
support or you can also try the many wonderful resources on the ADSM
listserv.

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

On Mon, Jul 26, 2010 at 7:13 AM, Prather, Wanda <wPrather AT icfi DOT com> 
wrote:

> I too have seen this happen in 6.1.3 - TSM will grow past the defined size
> of the active log.
>
> 1) contact support, they will help you with a procedure to get your server
> started again
>
> 2) in dsmserv.opt, add:  ALLOWREORGTABLE NO
> (It is usually the table reorgs that cause the logs to overflow.  I have
> been running a TSM server since January with no reorgs, and no problems.)
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Richard Sims
> Sent: Monday, July 26, 2010 7:15 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] servet 6.1.3.4 logs problem
>
> On Jul 26, 2010, at 4:36 AM, Hana Darzi wrote:
>
> > Hello all,
> >
> > I need help to this:
> > Windows server 2003 R2 sp2 64
> > Tivoli 6.1.3.4
> > The definition is Activelogsize 81920  (80Gb)
> > Actually size now is 136Gb (it is disk only to tsm active log) when the
> limit
> > Of tsm is 128Gb.
> >
> > I am in situation the I cannot give ACTIVELOGSIZE grater then 128Gb but I
> have
> > 136Gb logs and the server fails.
> >
> > What I can do?????
> > ...
>
> Can you find any evidence of a database backup being triggered to deal with
> the threshold event?  It's possible that such a backup is failing to happen
> for lack of tapes of the appropriate class or a drive/media problem which is
> causing the backup to become mired in block write retries or something
> similar.  If you can't find any evidence, you may need to confer with TSM
> Support.
>
>    Richard Sims
>