Looks like you have a normal mode for your  recovery log.
To use the dbb trigger, log has to be in roll forward mode.  Do q status
and see what the setting is.
I believe once you change it to roll forward, dbb trigger will be
automatically enabled.

If your log mode is normal I would try to investigate what or why is
causing the recovery log to fill up without setting back to 0.  In Normal
mode recovery log should not fill up that high unless there are many
activities going on the server.


Sung Y. Lee


"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 05/02/2006
01:29:43 PM:

> Hello Richard,
>
> I have since added a database backup trigger, but it says that it is
still
> disabled...  How do I go about enabling the trigger?  I didn't see an
> enable option.  Thanks!
>
> ********************************
> Joni Moyer
> Highmark
> Storage Systems, Senior Systems Programmer
> Phone Number: (717)302-9966
> Fax: (717) 302-9826
> joni.moyer AT highmark DOT com
> ********************************
>
>
>
>              "Richard Sims"
>              <rbs AT BU DOT EDU>
>              Sent by: "ADSM:
To
>              Dist Stor                 ADSM-L AT VM.MARIST DOT EDU
>              Manager"
cc
>              <[email protected]
>              .EDU>
Subject
>                                        Re: HELP!  Recovery log is almost
>                                        100% full!!!
>              05/02/2006 07:39
>              AM
>
>
>              Please respond to
>              "ADSM: Dist Stor
>                  Manager"
>              <[email protected]
>                    .EDU>
>
>
>
>
>
>
> Joni - See the many past discussions of this in the List archives.
>
> The 'SHow LOGPINned' command is typically helpful. And, certainly, it
> is client sessions which pin the log, while Expiration is the big
> process consumer.
>
> And it sounds like you don't have a DBBackuptrigger set up to protect
> the log.
>
>     Richard Sims
>
> On May 2, 2006, at 7:36 AM, Joni Moyer wrote:
>
> > Hello Everyone,
> >
> > I came in this morning and found that the recovery log is 99.1%
> > full!  I
> > have a TSM 5.2.7.1 server on AIX 5.2.  What, if anything, can I
> > check to
> > see that has the log so full?  Thanks in advance!