Hi Remco,

That's normal, that's how active logs work.  Only the archive log will be
purged after a database backup.

The active log includes transactions that are in-flight, that is that they
are currently running.  The only reason that they go away when you restart
the server is that when the server shuts down, it ends all the
transactions.  No transactions=no active logs.

Your server is working normally.  Just make sure you have sufficient active
log space and that the filesystem/LUN used for the active log is not shared
with anything.

-
Thanks,
Marc...
________________________________________________________
Marc Lanteigne
Accelerated Value Specialist for Spectrum Protect
416.478.0233 | marclanteigne AT ca.ibm DOT com
Office Hours:  Monday to Friday, 7:00 to 16:00 Eastern

Follow me on: Twitter, developerWorks, LinkedIn


-----Original Message-----
From: Remco Post [mailto:r.post AT PLCS DOT NL]
Sent: Thursday, November 9, 2017 7:59 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] log not flushing

Hi All,

for my current customer we’ve build a number of SP 8.1.1 servers. One thing
that is new is that sometimes the server doesn’t empty the DB2 active log
after a full database backup. The only way it seems that the log gets
flushed is by restarting the TSM server. I’ve seen this now 2 or 3 times in
the few months that we’re actively using these servers and it makes me feel
uneasy. And no, it’s not like the server is very busy, the server was
completely idle as far as I can see.

--

 Met vriendelijke groeten/Kind Regards,

Remco Post
r.post AT plcs DOT nl
+31 6 248 21 622