Author: "Choudarapu, Ramakrishna (GTI)" <Ramakrishna_Choudarapu AT ML DOT COM>
Date: Wed, 7 Feb 2007 12:09:39 -0500
Hi All, We had a recovery log pinning problem and the log was growing since last 4 days and currently is at 72% util... TSM Server 5.3.3.0 running on z/OS. Below is the SHOW LOGPINNED output: Dirty p
Author: Mark Stapleton <mark.s AT EVOLVINGSOL DOT COM>
Date: Wed, 7 Feb 2007 11:12:01 -0600
(snip) It looks like you're currently running a database backup; that should clear the log unless the pin is stubborn. If the db backup doesn't clear up your problem, you may want to consider taking
Author: "Choudarapu, Ramakrishna (GTI)" <Ramakrishna_Choudarapu AT ML DOT COM>
Date: Wed, 7 Feb 2007 12:24:15 -0500
Mark, Looks like this pin is 'stubborn', as the successful completion of the database backup for last three days, did not clear the log. AFAIK, this has not happened before. What would happen to the
Author: Mark Stapleton <mark.s AT EVOLVINGSOL DOT COM>
Date: Wed, 7 Feb 2007 11:34:50 -0600
What would happen to the uncommitted transactions if the TSM service is recycled? [SNIP] Can't say, although I've never lost any TSM db data when forced to run HALT on the server; I suspect that forc
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Wed, 7 Feb 2007 11:13:58 -0700
I might have missed it, but is there a long-running client operation in progress, or some other long-running process? That could be pinning the log. For example, a client backup of a very large file
Kinda weird...i had the exact same thing happen yesterday and I've never seen it before either. We had to halt/restart to fix the problem...... What would happen to the uncommitted transactions if th
Author: Richard Rhodes <rrhodes AT FIRSTENERGYCORP DOT COM>
Date: Wed, 7 Feb 2007 16:44:50 -0500
Same here, but our experience was a couple months ago. Rick "Park, Rod" <[email protected] OM> To Sent by: "ADSM: ADSM-L AT VM.MARIST DOT EDU Dist Stor cc Manager" <[email protected] Subject .EDU> Re:
Author: Vincent RATAJSZCZAK <vincent.ratajszczak AT RTE-FRANCE DOT COM>
Date: Mon, 14 Nov 2005 11:26:45 +0100
Hi TSM Cow Boys/Girls I would like to abuse of your busy time. I discover that 2 of my several servers have a recovery Log pinned. I use the TSM/ADSM QuickFacts which point me to "IBM site article sw
Vince I'm not sure where you got that reference number from, but my bookmarked page of Richard's quick facts gives the following references. IBM Technotes: 1084167; 1105651; 1105830 I have just done
Vince, I forgot something else, if it is 2 of your servers illustrating the same behaviour, the offending operation could be a server to server function that you may be running. Leigh -A TSM cowboy w