ADSM-L

Re: Recovery Log Full & No Access to ADSM

1998-04-23 21:01:40
Subject: Re: Recovery Log Full & No Access to ADSM
From: Trevor Foley <Trevor.Foley AT BANKERSTRUST.COM DOT AU>
Date: Fri, 24 Apr 1998 11:01:40 +1000
Hi Simon,

You need to format an additional recovery log using the DSMFMT utility.
It only needs to be small, maybe 10% of so of the existing log. Once
that is done, you then install that file with DSMSERV EXTEND DB. You can
find the full syntax for these command in appendix A (DSMFMT) and
appendix B (DSMSERVE EXTEND DB) of the ADSM Administrator's Reference.

You should then be able to start the server normally. However, you will
then need to work out why this happened. Do you have a database backup
trigger enabled? This will automatically trigger a database backup when
the log gets to more than a predefined % full.


Trevor

        -----Original Message-----
        From:   Simon Watson
[SMTP:Simon.S.Watson AT OPENMAIL.FIC32.BSPSER.SIMIS DOT COM]
        Sent:   Friday, April 24, 1998 10:32 AM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Recovery Log Full & No Access to ADSM

        We are just in the startup phase of ADSM and last night a rather
large
        client did it's full backup.  This morning none of our ADSM
passwords
        will give us access.  In addition we are getting the following
error
        message from the clients:

        "Session Rejected:
        The server doesn't have enough recovery log space to allow a
connection
        to be established."

        It is pretty obvious that the recovery log has filled up and it
is not
        allowing us access.  What is the recommended way to resolve this
problem?

        We are using AIX 4.2.1 and ADSM 3.1.0.0.

        Thanks for any help.

        Regards,
        Simon
<Prev in Thread] Current Thread [Next in Thread>