When I had this problem, several times, stopping and restarting the server
freed the pinned transaction log record.  The problem I had (on a older
level) was that the log file did not reduce after a database backup.  Other
things to consider is reducing your activity log retention value and to turn
off roll forward logging; at least until you figure out your problem.

On Mon, 11 Dec 2000, Vijay Havaralu wrote:

> Hello every one,
> We are running tsm-server ver 3.7.20 on aix 4.3.2 with about 400 gb per day
> backup.
> Our adsm db-size is close to 100 gb and growing daily.
> Almost each day log is overflowing with 100%, all backups fails, and server
> recovers & continues
> We are already using max 5.4 gb of log and can not increase any more on log
> volume.
>
> I appreciate, if anybody has any solutions this problem to reduce log usage
> or extend log beyond 5.4gb.
>
> Thanks, vijay.
>