I think that if the log is growing, it's from other sessions that are
still running. You should be able to cancel those without delay.
Before I halt a server, I always try to cancel all the active sessions and
give it 10-15 minutes to free up, while monitoring the log.
Seems to work for me.
Regar
> From what I understand, when you cancel the session, TSM rolls back
the
> transaction. Sometimes it's quick, sometimes it can take quite a
while.
> but the log won't grow any more from the session while it is rolling
back.
It may well be that the log isn't 'supposed" to grow but that isn't what
> Take a look also at the 'show logpinned cancel' command if that's not
what
> you used to cancel the session - sometimes it's helpful. If that
doesn't
> work then halting the server will do the trick, but that's not the
most
> tidy or convenient way... assuming you're about to run out of log and
- "Geoffrey L. Gill" wrote:
> For the past 2 days something has been screwing up backups by filling
> the log and this morning I remembered the show logpinned command and
> found the server that is causing it. I've cancelled the session but
> as
> far as I know am at the mercy of TSM to kill
>From what I understand, when you cancel the session, TSM rolls back the
transaction. Sometimes it's quick, sometimes it can take quite a while.
but the log won't grow any more from the session while it is rolling back.
Regards,
Shawn
Shawn Drew
