I have had this before run a *sh logpinned* this should show the process
or session which pins the log.  I would cancel that process or session
as its slowing down the whole TSM server, once stopped check that *sh
logpinned* has now gone, what can happen is another session or process
can take its place, so once again cancel them until *sh logpinned* shows
'nothing is pinning the log' this can free the log up, if not run DB
Backup and you should be back to normal.

You are in tricky situation DONT let your log blow up its not fun.

Good luck

Mark Stapleton wrote:

You likely have a backup session that is "pinning" the log in place
until the backup completes.

Create a TSM script that runs QUERY LOG >> <filename> every minute or
so. Examine the file every day to see if the same sort of thing happens
regularly. Note the timestamps, and discover what clients are backing up
when the log starts to grow.

Oh, and your company's email server spews an "address change" email to
everyone who responds to ADSM-L emails. You might want to have your mail
admin look into that.

--
Mark Stapleton (mark.stapleton AT cdw DOT com)
CDW Berbee
System engineer
7145 Boone Avenue North, Suite 140
Brooklyn Park MN 55428-1511
763-592-5963
www.berbee.com


From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
Of Jeff White

I have a query regarding some unusual activity a couple of nights ago.

Our recovery log is 12gb and is in NORNAL mode

I ran a full database backup at 16:00 Saturday - that should clear the
log down. During the night, the log appears to go to 80%. Or so the

following

messages indicated:

09-11-2008 05:18:59      ANR2997W The server log is 80 percent full.
The
server will delay transactions by 3 milliseconds. (SESSION: 1734316)
09-11-2008 05:26:51      ANR2997W The server log is 80 percent full.
The
server will delay transactions by 3 milliseconds.
09-11-2008 06:19:46      ANR2997W The server log is 80 percent full.
The
server will delay transactions by 3 milliseconds. (SESSION: 1744757)

Then

09-11-2008 06:19:49      ANR2996I The server log is 5 percent full.

The

server is no longer delaying transactions.(SESSION: 1734370)

The next full database did not run until approx. 16:00 on Sunday
afternoon.
So if the database backup did not clear the log to 5% used, what could
have.
There is no activity other than a few backups between the last

ANR2997W

message and the ANR2996I message.

Thoughts?

Jeff White