Yes,  the server will start terminating sessions at 100%.  If this resolves
the issue, it will usually recover, else it will core dump with a LOGSEG
error.
Jeff Bach
Home Office Open Systems Engineering
Wal-Mart Stores, Inc.

WAL-MART CONFIDENTIAL


        -----Original Message-----
        From:   Suad Musovich [SMTP:suad AT CCU1.AUCKLAND.AC DOT NZ]
        Sent:   Wednesday, May 30, 2001 1:29 AM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Re: Recovery log utilization does not drop after DB
backup

        > 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
        --


**********************************************************************
This email and any files transmitted with it are confidential
and intended solely for the individual or entity to
whom they are addressed.  If you have received this email
in error destroy it immediately.
**********************************************************************