We have seen this too.  I have not been able to figure out what causes the
log to fill up.  It seems to happen randomly.  Normally, the log doesn't get
more than 10-20% full, but every once in awhile it fills up.  My "solution"
to this problem is to keep a bit of extra space available, but not allocated
in the log.  When the log fills up, I simply "EXTEND LOG" to give it an
extra 4M of space.  This usually allows things to free up.  I have also
expanded the log (several times now, actually).  Not a great way to solve
the problem, but it does help.  Frankly, I think there is some sort of bug
or design deficiency lurking about here, as I don't think this is reasonable
behaviour for ADSM.

..Paul
--
On Fri, 13 Sep 1996 15:27:31 -0600 Bob Booth - CSO said:
On Fri, 13 Sep 1996 15:27:31 -0600 Bob Booth - CSO said:
>For the last two days, I have had the unfortunate experience of my recovery
>log filling and stopping all function of ADSM.  The only way that I can
>get it going, is to add more log space.  This is a fix, but there will be
>some day when I can't add log space.  How do I get the recover log to
>flush?  If I halt my server with a RL at 101% do I loose data, or does the
>RL flush?
>
>Does anyone know why the RL is filling?  It seems to be doing this at a
>seemingly idle period.  It has also started happening after going to R9
>just a few weeks ago.
>
>It is an AIX 3.2.5 server, running ADSM V2 R1 M9
>
>Any help would be appreciated!
>
>Bob