I had this several times on older levels.  In my case it ususally occurred
after a problem with the STK silo.  The only way I could get the log to
release was to stop and restart the server.

On Tue, 29 Aug 2000, Alex Paschal wrote:

> Bob,
>
> It's possible the one of the client sessions had pinned the tail of the
> recovery log, I've experienced that several times.  You might check to see
> if one of your client sessions had been running long, possibly with lots of
> waits.  I don't have any other ideas off the top of my head, unfortunately.
>
> Alex Paschal
> Storage Administrator
> Freightliner, LLC
> (503) 745-6850 phone/vmail
> (503) 745-5091 fax
>
> -----Original Message-----
> From: Brazner, Bob [mailto:Bob.Brazner AT JCI DOT COM]
> Sent: Tuesday, August 29, 2000 1:00 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Triggered DBB does not fully relieve the log
>
>
> We do a full db backup (BAckup DB) each day.  On some days however, we'll
> hit the DBB trigger threshold (65% with zero incrementals).  Recently, on
> one such day, after the triggered DB backup finished, we received the
> following message: "ANR4556W Warning: the database backup operation did not
> free sufficient recovery log space to lower utilization below the database
> backup trigger. The recovery log size may need to be increased."  The
> triggered DB backup otherwise finished successfully.  Further, it took
> aprox 2.3 hours to do the triggered db backup whereas it normally takes 40
> minutes to do a full backup.   Expiration did not run during this time.
> Normal client backup activity took place during this time.  Server is AIX
> 4.3.2 with ADSM 3.1.2.20.  What would account for this behavior?
>
> Bob Brazner
> (414) 524-2570
>