Re: Recovery log utilization does not drop after DB backup

2001-05-30 09:30:46
Subject: Re: Recovery log utilization does not drop after DB backup
From: Angela Hughes <hughesa1989 AT YAHOO DOT COM>
Date: Wed, 30 May 2001 06:31:41 -0700
This problem can also be eliminated by performing a
full DB backup daily which I've always done and if the
environment is very large with a lot of activity you
can perform incremental DB backups with the DB trigger
option throughout the day.

--- David Longo <David.Longo AT HEALTH-FIRST DOT ORG> wrote:
> When your recovery log hits 100%, basically one of
> When your recovery log hits 100%, basically one of
> two things happens.
> 1.  If there is "Available Space" greater than
> "Assigned Capacity" then log will acquire some of
> this additional space.
> 2.  When all space is consumed - TSM server crashes!
>  I have had this happen with server on AIX.
> Solution for that is to use OS level dsmfmt and
> dsmserv extend log to gain additional space so
> server can be restarted.
> David B. Longo
> System Administrator
> Health First, Inc.
> 3300 Fiske Blvd.
> Rockledge, FL 32955-4305
> PH      321.434.5536
> Pager  321.634.8230
> Fax:    321.434.5525
> david.longo AT health-first DOT org
> >>> suad AT CCU1.AUCKLAND.AC DOT NZ 05/30/01 02:28AM >>>
> > some time ago I complained in a mail to this list
> that the recovery log
> > utilization is not reset after a database backup.
> APAR IC30181 was generated
> > for this problem. Its status is "open".
> I complained about the problem too. The response I
> got was, when the system was
> too busy it took a while for it to happen.
> I have done this when no sessions/processes were
> running on the system and it still
> took over an hour to reset itself.
> Our situation is worse as sometimes the log jumps up
> to over 90% before we start to
> backup (triggered by a ANR0314W). It has continued
> to increase after the backup
> and has got to 98% in one observed instance. Will it
> stop sessions if it gets to 100?
> The reason we don't have a auto triggered backup is
> that we use a manual tape
> drive (LTO is a bit of a waste for incrementals).
> Suad
> --
> "MMS <>" made the following
>  annotations on 05/30/01 09:17:19
> This message is for the named person's use only.  It
> This message is for the named person's use only.  It
> may contain confidential, proprietary, or legally
> privileged information.  No confidentiality or
> privilege is waived or lost by any mistransmission.
> If you receive this message in error, please
> immediately delete it and all copies of it from your
> system, destroy any hard copies of it, and notify
> the sender.  You must not, directly or indirectly,
> use, disclose, distribute, print, or copy any part
> of this message if you are not the intended
> recipient.  Health First reserves the right to
> monitor all e-mail communications through its
> networks.  Any views or opinions expressed in this
> message are solely those of the individual sender,
> except (1) where the message states such views or
> opinions are on behalf of a particular entity;  and
> (2) the sender is authorized by the entity to give
> such views or opinions.

Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year!