Normally the trigger worked as expected, but I had a similar incident.  In
my case, after several dumps, the activity log was flooded with errors say
it could read some log items.  Eventually the host ran out of paging space
and crashed.

One suggestion from the list (not IBM), which I implemented, was that the
trigger should not be less that 75%.  I also increased the size of the log
file so as to minimize triggered dumps.

On Mon, 22 Mar 1999, Richard Sims wrote:

> >Time after time, a database backup was triggered almost immediately after
> >the last one completed. This happened 12 times before the system (probably)
> >ran out of scratch tapes:
> >Why does this happen?
>
> The Recovery Log having reached the DBBackuptrigger value, especially
> repeatedly, is obviously a symptom of a LOT of activity.  What sessions
> were active?  What was going on?  Look at your Activity Log and
> accounting records for client activity.
>     Richard Sims, BU
>