Re: logpinned
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. Regards, Shawn Shawn Drew Internet geoffrey.l.g...@saic.com Sent by: ADSM-L@VM.MARIST.EDU 11/11/2009 02:20 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject Re: [ADSM-L] logpinned > 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 I experienced. I ended up halting TSM and restarting as I did not want to take a chance that it would fill completely even though I do have headroom to extend the log further. The administrator of the server tells me he stopped all TSM services that were running but that didn't seem to cancel the sessions either, and I thought it would. If it was supposed to then I'd have to question the system he was on. Geoff Gill TSM/PeopleSoft Administrator SAIC M/S-B1P 4224 Campus Pt. Ct. San Diego, CA 92121 (858)826-4062 (office) (858)412-9883 (blackberry) This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
Re: logpinned
> 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 I experienced. I ended up halting TSM and restarting as I did not want to take a chance that it would fill completely even though I do have headroom to extend the log further. The administrator of the server tells me he stopped all TSM services that were running but that didn't seem to cancel the sessions either, and I thought it would. If it was supposed to then I'd have to question the system he was on. Geoff Gill TSM/PeopleSoft Administrator SAIC M/S-B1P 4224 Campus Pt. Ct. San Diego, CA 92121 (858)826-4062 (office) (858)412-9883 (blackberry)
Re: logpinned
> 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 > crash anyway... Yes, been there done that. It basically does a cancel se. Geoff Gill TSM/PeopleSoft Administrator SAIC M/S-B1P 4224 Campus Pt. Ct. San Diego, CA 92121 (858)826-4062 (office) (858)412-9883 (blackberry)
Re: logpinned
- "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 it at some point. I > contacted the administrator and they shut down the services but the > sessions still seem to hang out there. > > 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 crash anyway...
Re: logpinned
>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 Internet geoffrey.l.g...@saic.com Sent by: ADSM-L@VM.MARIST.EDU 11/11/2009 12:48 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] logpinned 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 it at some point. I contacted the administrator and they shut down the services but the sessions still seem to hang out there. Geoff Gill TSM/PeopleSoft Administrator SAIC M/S-B1P 4224 Campus Pt. Ct. San Diego, CA 92121 (858)826-4062 (office) (858)412-9883 (blackberry) This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
