I might have missed it, but is there a long-running client operation in
progress, or some other long-running process? That could be pinning the
log. For example, a client backup of a very large file over a modem.

The SHOW LOGPINNED command might shed some light (support would probably
want that info anyway).

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 02/07/2007
10:34:50 AM:

> From: ADSM: Dist Stor Manager on behalf of Choudarapu, Ramakrishna (GTI)
> Looks like this pin is 'stubborn', as the successful completion of the
> database backup for last three days, did not clear the log. AFAIK, this
> has not happened before.
>
> What would happen to the uncommitted transactions if the TSM service is
> recycled?
>
> [SNIP]
>
> Can't say, although I've never lost any TSM db data when forced to
> run HALT on the server; I suspect that forces a log commit as part
> of an orderly shutdown.
>
> If you've got time, I'd log a call with Tivoli support and set a
> ticket for this. They may want to gather some data on the situation,
> time and your situation permitting. This is the first "stubborn" log
> pin with no obvious cause I've heard of since 5.3 came into being.
>
> What size is your recovery log?
>
> --
> Mark Stapleton (mark.s AT evolvingsol DOT com)
> Senior consultant