ADSM-L

Re: Recovery log problem

1999-09-01 11:14:09
Subject: Re: Recovery log problem
From: Joshua Bassi <jbassi AT GLORYWORKS DOT COM>
Date: Wed, 1 Sep 1999 08:14:09 -0700
Valeriano,

I have seen this before.

What I think it is is another process such as a backup/restore,
migration, etc will have data locked in the recovery log until the
transaction completes.  Then when the DB backup completes, ADSM will
not free up any rec log space because this external process hasn't
finished what it was doing and won't commit it's rec log record to
the DB.  It's a vicious cycle!

> BTW, data base backup trigger is at 80%

IMHO that is a bit high.  If DB space isn't freed fast enough your
server will come down, and you will have to cut your vacation on those
Italian beaches short :-)  I would recommend a 60-70 DB backuptrigger.


Joshua S. Bassi
Storage Management Team Lead
Tivoli Certified Consultant - ADSM V3
IBM Certified Specialist - AIX and
Mid-Range Storage Technical Solutions
Dickens Services Group
(404) 386-9848
jbassi AT gloryworks DOT com
www.TeamDSG.com

<Prev in Thread] Current Thread [Next in Thread>