John,

We had similar problems a while back. I can report that filling the
recovery log has unpredictable but invariable awful consequences such as
the server going down or becoming inoperational. You can set a database
backup trigger to start backing up the database and 'flush' the recovery
log when the recovery log gets to say 60% utilisation. This didn't help us
as the recovery log managed to fill up before the db backup had completed.
We got around the problem by rescheduling the operations which were causing
the recovery log to fill so fast in the first place. (we couldn't extend
the log, it's already 5GB and can only be made a little bit bigger). So the
recovery log still grows just as much, its just that it does so over a
longer period of time and the triggered db backup has time to complete
before disaster strikes.

Regards,

Eric Winters
IBM Global Services Australia
ZE06 (Zenith Centre - Tower A)
Level 6,
821 Pacific Highway
Chatswood NSW 2067
Sydney Australia
Ph:  +61-2-8448 4104
Fax: +61-2-8448 4006


"Doherty, John (ANFIS)" <jdohe1 AT ANFIS.CO DOT UK> on 29/03/2000 22:26:04

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Eric Winters/Australia/Contr/IBM)
Subject:  Recovery Log




Can anyone tell me how best to manage space in the recovery log and DB.

Last night I received the following messages:

03/29/2000 05:28:38 ANR0314W Recovery log usage exceeds 90 % of its
assigned
capacity.
03/29/2000 05:30:50 ANR0314W Recovery log usage exceeds 92 % of its
assigned
capacity.
03/29/2000 05:33:03 ANR0314W Recovery log usage exceeds 94 % of its
assigned
capacity.
03/29/2000 05:35:22 ANR0314W Recovery log usage exceeds 96 % of its
assigned
capacity.
03/29/2000 05:38:06 ANR0314W Recovery log usage exceeds 98 % of its
assigned
capacity.

What is the normal course of events if the above happens ?

I realise I can extend the recovery log.  But how do I know if it is being
utilised properly.  I have also noticed that the utilisation counters have
not been reset since 22/06/98.  Is this a problem.

A display of my log file is as follows:

ANS8000I Server command: 'QUERY LOG F=D'
       Available Space (MB): 592
     Assigned Capacity (MB): 592
     Maximum Extension (MB): 0
     Maximum Reduction (MB): 584
          Page Size (bytes): 4,096
         Total Usable Pages: 151,040
                 Used Pages: 337
                   Pct Util: 0.2
              Max. Pct Util: 100.3
           Physical Volumes: 4
             Log Pool Pages: 128
         Log Pool Pct. Util: 3.34
         Log Pool Pct. Wait: 0.22
Cumulative Consumption (MB): 722,834.19
Consumption Reset Date/Time: 06/22/1998 15:10:41

Looking at the above should I extend my log ?


> John Doherty. Tel:   +44   (0)   141 275 7793
>               Fax:  +44   (0)   141 275 9199
>               Email: JDohe1 AT Anfis.co DOT uk
>
>       Technical Specialist, Storage Management L02S
>
> Email communications are not necessarily secure and may be intercepted or
> changed after they are sent.  Abbey National Financial and Investment
> Services  does not accept liability for any such changes. If you wish to
> confirm the origin or content of this communication, please contact the
> sender using an alternative means of communication.  This communication
> does not create or modify any contract.  If you are not the intended
> recipient of this communication you should destroy it without copying,
> disclosing or otherwise using its contents.  Please notify the sender
> immediately of the error.
>
> ABBEY NATIONAL FINANCIAL AND INVESTMENT SERVICES plc
>         Registered Office Abbey National House 287 St Vincent Street
>         Glasgow G2 5NB United Kingdom Registered in Scotland No 159852
>