As Paul said, you've most likely got a long running session or process that
has a transaction pinning the log. I've got a cron'd script that runs every
10 minutes that logs to an alog. This is a cirular log that won't grow out
of control even if you never check it. This helps me figure out what's
causing my pinned recovery log on the rare occassion it happens. A simple
example is included below.
Alex Paschal
Storage Administrator
Freightliner, LLC
(503) 745-6850 phone/vmail
!#/usr/bin/ksh
{
echo "q sess"
echo "q pr"
echo "q log"
} | dsmadmc -id=id -pa=password | alog -q -f /path/logname -s 200000
-----Original Message-----
From: Richard Foster [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 03, 2002 7:27 AM
To: [EMAIL PROTECTED]
Subject: Our log fills up and server crashes
Anyone seen this before?
Our TSM server has crashed 3 nights running with a full log. We started
with Logmode=Rollforward and 3960 MB log. We tried increasing to 6012 MB,
which delayed the crash by about 45 mins.
We have DB backup trigger at 60%. But even when the backup ran, we got msg
"ANR4556W Attention: the database backup operation did not free sufficient
recovery log space to lower utilization below the database backup trigger.
The recovery log size may need to be increased." I guess this indicates a
transaction which is out of control - but I can't identify which TXN it is.
We have now switched to Logmode=normal, but I'm not sure it'll help.
Setup: TSM server 4.2.1.11 running on AIX 4.3.3 plus ML9 and patches.
Clients on NetWare, Windows, Unix (various flavours), plus TDP for R/3.
Any comments, suggestions, etc received gratefully.
Richard Foster
