Trying to delete a filespace???
Hi all I'm trying to delete the following filespace and having no luck at all. The command I'm using is as below and I'm not getting any joy. Any ideas? Regards Farren delete filespace CHI-AS-SCCMEUR CHI-AS-SCCMEUR\SystemState\NULL\SystemState\SystemState type=any namet=uni Node Name: CHI-AS-SCCMEUR Filespace Name: CHI-AS-SCCMEUR\SystemState\NULL\System State\SystemState Hexadecimal Filespace Name: 4348492d41532d5343434d425c53797374656d5- 3746174655c4e554c4c5c53797374656d205374617- 4655c53797374656d5374617465 FSID: 7 Platform: WinNT Filespace Type: VSS Is Filespace Unicode?: Yes Capacity (MB): 0.0 Pct Util: 0.0 Last Backup Start Date/Time: 05/13/11 18:28:59 Days Since Last Backup Started: 3 Last Backup Completion Date/Time: 05/14/11 00:45:55 Days Since Last Backup Completed: 2 Last Full NAS Image Backup Completion Date/Time: John Wiley & Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, United Kingdom. PO19 8SQ.
Ang: Trying to delete a filespace???
Hi What is the result you're getting from executing the delete filespace command? Are you getting an error? Or are you getting a successful completion state but the filespace is still there? It would be helpful if you also told us the result from executing the command. Have you tried doing "delete filespace CHI-AS-SCCMEUR 7 nametype=fsid" ? Best Regards Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: "Minns, Farren - Chichester" Sänt av: "ADSM: Dist Stor Manager" Datum: 05/16/2011 11:09 Ärende: Trying to delete a filespace??? Hi all I'm trying to delete the following filespace and having no luck at all. The command I'm using is as below and I'm not getting any joy. Any ideas? Regards Farren delete filespace CHI-AS-SCCMEUR CHI-AS-SCCMEUR\SystemState\NULL\SystemState\SystemState type=any namet=uni Node Name: CHI-AS-SCCMEUR Filespace Name: CHI-AS-SCCMEUR\SystemState\NULL\System State\SystemState Hexadecimal Filespace Name: 4348492d41532d5343434d425c53797374656d5- 3746174655c4e554c4c5c53797374656d205374617- 4655c53797374656d5374617465 FSID: 7 Platform: WinNT Filespace Type: VSS Is Filespace Unicode?: Yes Capacity (MB): 0.0 Pct Util: 0.0 Last Backup Start Date/Time: 05/13/11 18:28:59 Days Since Last Backup Started: 3 Last Backup Completion Date/Time: 05/14/11 00:45:55 Days Since Last Backup Completed: 2 Last Full NAS Image Backup Completion Date/Time: John Wiley & Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, United Kingdom. PO19 8SQ.
Re: Trying to delete a filespace???
Try namet=fsid and use filespace ID instead of name. FSID can be taken from "q fi f=d". You will avoid a lot of problems with cpecial characters in filespace name. Grigori G. Solonovitch -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Minns, Farren - Chichester Sent: Monday, May 16, 2011 12:10 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Trying to delete a filespace??? Hi all I'm trying to delete the following filespace and having no luck at all. The command I'm using is as below and I'm not getting any joy. Any ideas? Regards Farren delete filespace CHI-AS-SCCMEUR CHI-AS-SCCMEUR\SystemState\NULL\SystemState\SystemState type=any namet=uni Node Name: CHI-AS-SCCMEUR Filespace Name: CHI-AS-SCCMEUR\SystemState\NULL\System State\SystemState Hexadecimal Filespace Name: 4348492d41532d5343434d425c53797374656d5- 3746174655c4e554c4c5c53797374656d205374617- 4655c53797374656d5374617465 FSID: 7 Platform: WinNT Filespace Type: VSS Is Filespace Unicode?: Yes Capacity (MB): 0.0 Pct Util: 0.0 Last Backup Start Date/Time: 05/13/11 18:28:59 Days Since Last Backup Started: 3 Last Backup Completion Date/Time: 05/14/11 00:45:55 Days Since Last Backup Completed: 2 Last Full NAS Image Backup Completion Date/Time: John Wiley & Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, United Kingdom. PO19 8SQ. Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
Re: Trying to delete a filespace???
Thanks Grigori
I was missing a space { NULL\System State }, so the below command worked.
Thanks for your advice though. I'll try that next time :-/
Regards
Farren
delete filespace CHI-AS-SCCMEUR 'CHI-AS-SCCMEUR\SystemState\NULL\System
State\SystemState' namet=uni
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Grigori Solonovitch
Sent: 16 May 2011 10:26
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Trying to delete a filespace???
Try namet=fsid and use filespace ID instead of name.
FSID can be taken from "q fi f=d".
You will avoid a lot of problems with cpecial characters in filespace name.
Grigori G. Solonovitch
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Minns,
Farren - Chichester
Sent: Monday, May 16, 2011 12:10 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Trying to delete a filespace???
Hi all
I'm trying to delete the following filespace and having no luck at all.
The command I'm using is as below and I'm not getting any joy.
Any ideas?
Regards
Farren
delete filespace CHI-AS-SCCMEUR
CHI-AS-SCCMEUR\SystemState\NULL\SystemState\SystemState type=any namet=uni
Node Name: CHI-AS-SCCMEUR
Filespace Name:
CHI-AS-SCCMEUR\SystemState\NULL\System
State\SystemState
Hexadecimal Filespace Name:
4348492d41532d5343434d425c53797374656d5-
3746174655c4e554c4c5c53797374656d205374617-
4655c53797374656d5374617465
FSID: 7
Platform: WinNT
Filespace Type: VSS
Is Filespace Unicode?: Yes
Capacity (MB): 0.0
Pct Util: 0.0
Last Backup Start Date/Time: 05/13/11 18:28:59
Days Since Last Backup Started: 3
Last Backup Completion Date/Time: 05/14/11 00:45:55
Days Since Last Backup Completed: 2
Last Full NAS Image Backup Completion Date/Time:
John Wiley & Sons Limited is a private limited company registered in England
with registered number 641132.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex,
United Kingdom. PO19 8SQ.
Please consider the environment before printing this Email.
CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail
message and any attachments hereto may be legally privileged and confidential.
The information is intended only for the recipient(s) named in this message. If
you are not the intended recipient you are notified that any use, disclosure,
copying or distribution is prohibited. If you have received this in error
please contact the sender and delete this message and any attachments from your
computer system. We do not guarantee that this message or any attachment to it
is secure or free from errors, computer viruses or other conditions that may
damage or interfere with data, hardware or software.
John Wiley & Sons Limited is a private limited company registered in England
with registered number 641132.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex,
United Kingdom. PO19 8SQ.
Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
Hi Richard! > So is 5.5.5.0 also having this issue with the log pinning? Yes. As soon as the log hist 80% TSM starts delaying transactions. In this level a bug was fixed which caused the log to fill too soon after it reached 80%. I'm running 5.5.5.2 and it's still filling to 80% multiple times a night. Kind regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Cheung, Richard Sent: zondag 15 mei 2011 04:02 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code Hi The worry about this is I had a PMR opened for this issue on my servers, which are currently at 5.5.4. I was advised it's a known issue, refer to APAR IC64438, and the recommended fix is to go to 5.5.5.0 So is 5.5.5.0 also having this issue with the log pinning? I also believed this was happening in early versions of TSM v6.. But the later builds are okay - can anyone confirm? Richard Cheung | Server Engineer | Information Systems | Santos Limited Santos Centre | 60 Flinders Street Adelaide SA 5000 Australia Ph +61 8 8116 7125 | 7 Fax +61 8 8116 5073 | richard.che...@santos.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Dave Canan Sent: Saturday, 14 May 2011 1:22 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code Andy Raibeck and I have been monitoring this thread for the past few weeks and have been having numerous discussions about what we need to do to address these problems. In addition, we have noted the many PMRs coming into the IBM support queue, and many of these PMRs are now on my queue. Andy will be assisting me along with other support people as needed. As part of this analysis we will be doing, we have a new questionnaire (titled "Items to Gather for a PMR with Log Pinning Condition for TSM V5") that customers will be filling out that ask several questions regarding your environment. We understand that this involves extra work to gather this information, but there can be many different areas that can cause log pinning conditions, so this information is needed. In addition, there will be a script provided (named serverperf5a.pl) that will help us gather additional data. Both of these will be provided to you by support. When these PMRs are now opened, please make sure that level 1 support adds the keyword LOGPIN55 to the PMR. This will allow Andy and I to quickly find all the PMRs being worked for this issue. Eric, your PMR is now one that I have on my queue (or I will shortly today). We will be contacting you to work the PMR. Dave Canan IBM ATS TSM Performance ddcananATUSDOTIBMDOTCOM 916-723-2410 On Thu, May 12, 2011 at 7:53 AM, Loon, EJ van - SPLXO wrote: > Hi Rick! > You are running in normal mode. In this mode the recovery log only > contains uncommited transactions. Don't you agree that in this case, > the log should NEVER reach 90%? It should not even reach something like 40%! > I don't want to have to implement extra monitoring to keep TSM from > crashing. It should just work. Like it did when we were running 5.3... > Kind regards, > Eric van Loon > KLM Royal Dutch Airlines > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of Richard Rhodes > Sent: donderdag 12 mei 2011 15:04 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code > > I have a cron job that checks log utilization every 15m. If the log > goes over 90% the scripts displays a bunch of stuff (q sess, q proc, q > log, show logpin, etc), runs a show logpin cancel, displays the > stuff again, > and finally emails me. (We run in normal mode.) It's been very > effective > in preventing a log full condition. > > rick > > > > > > > From: "Bos, Karel" > To: ADSM-L@VM.MARIST.EDU > Date: 05/12/2011 06:11 AM > Subject:Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 > code > Sent by:"ADSM: Dist Stor Manager" > > > > Hi, > > Dunno if u already looked at these options: THROUGHPUTDATATHRESHOLD > and THROUGHPUTTIMETHRESHOLD. After a couple of crashes due to log > filling up, a couple of years back, I standard added them to all my > clients (with low values to only kill the slowest/hung ones) and > untill now never had any issues with the V5.5 and below log space > under normal backup loads. > > Log filling only happend when some sys admin made some changes to the > biggest file servers we had but even this was handled like it should > be done by ITSM. > > Regards, > > Karel > > > > > Van: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] namens Loon, EJ > van > - > SPLXO [eric-van.l...@klm.com] > Verzonden: donderdag 12 mei 2011 11:11 > Aan: ADSM-L@VM.MARIST.EDU > Onderwerp: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 > code > > Hi Pau
Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
Rookie Question, What is Log Pinning? -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Loon, EJ van - SPLXO Sent: Monday, May 16, 2011 10:19 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code Hi Richard! > So is 5.5.5.0 also having this issue with the log pinning? Yes. As soon as the log hist 80% TSM starts delaying transactions. In this level a bug was fixed which caused the log to fill too soon after it reached 80%. I'm running 5.5.5.2 and it's still filling to 80% multiple times a night. Kind regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Cheung, Richard Sent: zondag 15 mei 2011 04:02 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code Hi The worry about this is I had a PMR opened for this issue on my servers, which are currently at 5.5.4. I was advised it's a known issue, refer to APAR IC64438, and the recommended fix is to go to 5.5.5.0 So is 5.5.5.0 also having this issue with the log pinning? I also believed this was happening in early versions of TSM v6.. But the later builds are okay - can anyone confirm? Richard Cheung | Server Engineer | Information Systems | Santos Limited Santos Centre | 60 Flinders Street Adelaide SA 5000 Australia Ph +61 8 8116 7125 | 7 Fax +61 8 8116 5073 | richard.che...@santos.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Dave Canan Sent: Saturday, 14 May 2011 1:22 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code Andy Raibeck and I have been monitoring this thread for the past few weeks and have been having numerous discussions about what we need to do to address these problems. In addition, we have noted the many PMRs coming into the IBM support queue, and many of these PMRs are now on my queue. Andy will be assisting me along with other support people as needed. As part of this analysis we will be doing, we have a new questionnaire (titled "Items to Gather for a PMR with Log Pinning Condition for TSM V5") that customers will be filling out that ask several questions regarding your environment. We understand that this involves extra work to gather this information, but there can be many different areas that can cause log pinning conditions, so this information is needed. In addition, there will be a script provided (named serverperf5a.pl) that will help us gather additional data. Both of these will be provided to you by support. When these PMRs are now opened, please make sure that level 1 support adds the keyword LOGPIN55 to the PMR. This will allow Andy and I to quickly find all the PMRs being worked for this issue. Eric, your PMR is now one that I have on my queue (or I will shortly today). We will be contacting you to work the PMR. Dave Canan IBM ATS TSM Performance ddcananATUSDOTIBMDOTCOM 916-723-2410 On Thu, May 12, 2011 at 7:53 AM, Loon, EJ van - SPLXO wrote: > Hi Rick! > You are running in normal mode. In this mode the recovery log only > contains uncommited transactions. Don't you agree that in this case, > the log should NEVER reach 90%? It should not even reach something like 40%! > I don't want to have to implement extra monitoring to keep TSM from > crashing. It should just work. Like it did when we were running 5.3... > Kind regards, > Eric van Loon > KLM Royal Dutch Airlines > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of Richard Rhodes > Sent: donderdag 12 mei 2011 15:04 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code > > I have a cron job that checks log utilization every 15m. If the log > goes over 90% the scripts displays a bunch of stuff (q sess, q proc, q > log, show logpin, etc), runs a show logpin cancel, displays the > stuff again, > and finally emails me. (We run in normal mode.) It's been very > effective > in preventing a log full condition. > > rick > > > > > > > From: "Bos, Karel" > To: ADSM-L@VM.MARIST.EDU > Date: 05/12/2011 06:11 AM > Subject:Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 > code > Sent by:"ADSM: Dist Stor Manager" > > > > Hi, > > Dunno if u already looked at these options: THROUGHPUTDATATHRESHOLD > and THROUGHPUTTIMETHRESHOLD. After a couple of crashes due to log > filling up, a couple of years back, I standard added them to all my > clients (with low values to only kill the slowest/hung ones) and > untill now never had any issues with the V5.5 and below log space > under normal backup loads. > > Log filling only happend when some sys admin made some changes to the > biggest file servers we had but even this was handled like it should > be done by ITSM. > > Regards, > > Karel >
Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
Hi Dave! Thank you VERY VERY much for your help I'm indeed contacted by your colleague, I filled the document and the script is currently collecting data. I'm absolutely willing to do the extra work, if it helps IBM fixing this issue, no problem! Thanks again! Kind regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Dave Canan Sent: vrijdag 13 mei 2011 17:52 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code Andy Raibeck and I have been monitoring this thread for the past few weeks and have been having numerous discussions about what we need to do to address these problems. In addition, we have noted the many PMRs coming into the IBM support queue, and many of these PMRs are now on my queue. Andy will be assisting me along with other support people as needed. As part of this analysis we will be doing, we have a new questionnaire (titled "Items to Gather for a PMR with Log Pinning Condition for TSM V5") that customers will be filling out that ask several questions regarding your environment. We understand that this involves extra work to gather this information, but there can be many different areas that can cause log pinning conditions, so this information is needed. In addition, there will be a script provided (named serverperf5a.pl) that will help us gather additional data. Both of these will be provided to you by support. When these PMRs are now opened, please make sure that level 1 support adds the keyword LOGPIN55 to the PMR. This will allow Andy and I to quickly find all the PMRs being worked for this issue. Eric, your PMR is now one that I have on my queue (or I will shortly today). We will be contacting you to work the PMR. Dave Canan IBM ATS TSM Performance ddcananATUSDOTIBMDOTCOM 916-723-2410 On Thu, May 12, 2011 at 7:53 AM, Loon, EJ van - SPLXO wrote: > Hi Rick! > You are running in normal mode. In this mode the recovery log only > contains uncommited transactions. Don't you agree that in this case, the > log should NEVER reach 90%? It should not even reach something like 40%! > I don't want to have to implement extra monitoring to keep TSM from > crashing. It should just work. Like it did when we were running 5.3... > Kind regards, > Eric van Loon > KLM Royal Dutch Airlines > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Richard Rhodes > Sent: donderdag 12 mei 2011 15:04 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code > > I have a cron job that checks log utilization every 15m. If the log > goes > over 90% the scripts displays a bunch of stuff (q sess, q proc, q log, > show logpin, etc), runs a show logpin cancel, displays the stuff > again, > and finally emails me. (We run in normal mode.) It's been very > effective > in preventing a log full condition. > > rick > > > > > > > From: "Bos, Karel" > To: ADSM-L@VM.MARIST.EDU > Date: 05/12/2011 06:11 AM > Subject:Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 > code > Sent by:"ADSM: Dist Stor Manager" > > > > Hi, > > Dunno if u already looked at these options: THROUGHPUTDATATHRESHOLD and > THROUGHPUTTIMETHRESHOLD. After a couple of crashes due to log filling > up, > a couple of years back, I standard added them to all my clients (with > low > values to only kill the slowest/hung ones) and untill now never had any > issues with the V5.5 and below log space under normal backup loads. > > Log filling only happend when some sys admin made some changes to the > biggest file servers we had but even this was handled like it should be > done by ITSM. > > Regards, > > Karel > > > > > Van: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] namens Loon, EJ van > - > SPLXO [eric-van.l...@klm.com] > Verzonden: donderdag 12 mei 2011 11:11 > Aan: ADSM-L@VM.MARIST.EDU > Onderwerp: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code > > Hi Paul! > We are already running 5.5.5.2 and the log is still filling up, even > after switching from rollforward to normal mode. > Management currently is questioning whether TSM is the right product for > the future. Although I'm a big fan of TSM for 15 years, I'm really in > doubt too... > Kind regards, > Eric van Loon > KLM Royal Dutch Airlines > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Paul Fielding > Sent: woensdag 11 mei 2011 20:05 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code > > Hi folks, if this has already been commented on, my apologies, I hvaen't > been following closely but just noticed this thread. > > We were experiencing log pinned issues after upgrading to 5.5.0.0 code > at > one of my client sites. What we were finding was that, occasionally, > I'd
Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
Answer to rookie question: All files backed up create an entry in the transaction log. When the file backup is complete the entry is eligible to be written to the database. TSM only writes the oldest entry in the transaction log. If a file backup takes a long time it can become the oldest entry in the log. Any new entries for backed-up files are stored in the log until the long-running file backup is complete. This is called log pinning. If the backup for one file takes too long the transaction log can become more than 80% full, at which time TSM slows down its backup process to allow transaction log processing to complete. If the transaction log becomes completely full, TSM processing stops. Hope this helps, Jim Schneider -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Mark Mooney Sent: Monday, May 16, 2011 11:23 AM To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code Rookie Question, What is Log Pinning? -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Loon, EJ van - SPLXO Sent: Monday, May 16, 2011 10:19 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code Hi Richard! > So is 5.5.5.0 also having this issue with the log pinning? Yes. As soon as the log hist 80% TSM starts delaying transactions. In this level a bug was fixed which caused the log to fill too soon after it reached 80%. I'm running 5.5.5.2 and it's still filling to 80% multiple times a night. Kind regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Cheung, Richard Sent: zondag 15 mei 2011 04:02 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code Hi The worry about this is I had a PMR opened for this issue on my servers, which are currently at 5.5.4. I was advised it's a known issue, refer to APAR IC64438, and the recommended fix is to go to 5.5.5.0 So is 5.5.5.0 also having this issue with the log pinning? I also believed this was happening in early versions of TSM v6.. But the later builds are okay - can anyone confirm? Richard Cheung | Server Engineer | Information Systems | Santos Limited Santos Centre | 60 Flinders Street Adelaide SA 5000 Australia Ph +61 8 8116 7125 | 7 Fax +61 8 8116 5073 | richard.che...@santos.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Dave Canan Sent: Saturday, 14 May 2011 1:22 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code Andy Raibeck and I have been monitoring this thread for the past few weeks and have been having numerous discussions about what we need to do to address these problems. In addition, we have noted the many PMRs coming into the IBM support queue, and many of these PMRs are now on my queue. Andy will be assisting me along with other support people as needed. As part of this analysis we will be doing, we have a new questionnaire (titled "Items to Gather for a PMR with Log Pinning Condition for TSM V5") that customers will be filling out that ask several questions regarding your environment. We understand that this involves extra work to gather this information, but there can be many different areas that can cause log pinning conditions, so this information is needed. In addition, there will be a script provided (named serverperf5a.pl) that will help us gather additional data. Both of these will be provided to you by support. When these PMRs are now opened, please make sure that level 1 support adds the keyword LOGPIN55 to the PMR. This will allow Andy and I to quickly find all the PMRs being worked for this issue. Eric, your PMR is now one that I have on my queue (or I will shortly today). We will be contacting you to work the PMR. Dave Canan IBM ATS TSM Performance ddcananATUSDOTIBMDOTCOM 916-723-2410 On Thu, May 12, 2011 at 7:53 AM, Loon, EJ van - SPLXO wrote: > Hi Rick! > You are running in normal mode. In this mode the recovery log only > contains uncommited transactions. Don't you agree that in this case, > the log should NEVER reach 90%? It should not even reach something like 40%! > I don't want to have to implement extra monitoring to keep TSM from > crashing. It should just work. Like it did when we were running 5.3... > Kind regards, > Eric van Loon > KLM Royal Dutch Airlines > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of Richard Rhodes > Sent: donderdag 12 mei 2011 15:04 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code > > I have a cron job that checks log utilization every 15m. If the log > goes over 90% the scripts displays a bunch of stuff (q sess, q proc, q > log, show logpin, etc), runs a
Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
Hi Eric (and others following this thread), Just to clarify: we are not aware of any code defects in the TSM 5.5.5 server that would contribute to recovery log pin situations. Rather, it is likely related to workload. But having said that, we do not dismiss any possibility out of hand. Some things that can pin the recovery log: - Windows 2008, Windows 2008 R2, Windows 7 and Windows Vista system state backups using the 6.2 client can cause the recovery log to pin during the object assignment phase of the backup - NDMP backups that span more than one tape (the pin occurs at the time the first tape starts to rewind and another tape is needed) - BACKUP IMAGE operations that span more than one tape (similar situation as NDMP) - Data Protection for * products, typically with large transactions that pin the log until the transaction is committed Of course there can be other reasons as well. It may very well be that others who responds "me too" to this post, could be experiencing the recovery log pin for different reasons. Or we might actually uncover a code-related issue... it all remains to be determined. Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager "ADSM: Dist Stor Manager" wrote on 2011-05-16 10:14:15: > From: "Loon, EJ van - SPLXO" > To: ADSM-L@vm.marist.edu > Date: 2011-05-16 13:13 > Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code > Sent by: "ADSM: Dist Stor Manager" > > Hi Dave! > Thank you VERY VERY much for your help > I'm indeed contacted by your colleague, I filled the document and the > script is currently collecting data. I'm absolutely willing to do the > extra work, if it helps IBM fixing this issue, no problem! > Thanks again! > Kind regards, > Eric van Loon > KLM Royal Dutch Airlines > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Dave Canan > Sent: vrijdag 13 mei 2011 17:52 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code > > Andy Raibeck and I have been monitoring this thread for the past few > weeks > and have been having numerous discussions about what we need to do to > address these problems. In addition, we have noted the many PMRs coming > into > the IBM support queue, and many of these PMRs are now on my queue. Andy > will > be assisting me along with other support people as needed. > > As part of this analysis we will be doing, we have a new questionnaire > (titled "Items to Gather for a PMR with Log Pinning Condition for TSM > V5") > that customers will be filling out that ask several questions regarding > your > environment. We understand that this involves extra work to gather this > information, but there can be many different areas that can cause log > pinning conditions, so this information is needed. In addition, there > will > be a script provided (named serverperf5a.pl) that will help us gather > additional data. Both of these will be provided to you by support. When > these PMRs are now opened, please make sure that level 1 support adds > the > keyword LOGPIN55 to the PMR. This will allow Andy and I to quickly find > all > the PMRs being worked for this issue. > > Eric, your PMR is now one that I have on my queue (or I will shortly > today). > We will be contacting you to work the PMR. > > Dave Canan > IBM ATS TSM Performance > ddcananATUSDOTIBMDOTCOM > 916-723-2410 > > On Thu, May 12, 2011 at 7:53 AM, Loon, EJ van - SPLXO > > wrote: > > > Hi Rick! > > You are running in normal mode. In this mode the recovery log only > > contains uncommited transactions. Don't you agree that in this case, > the > > log should NEVER reach 90%? It should not even reach something like > 40%! > > I don't want to have to implement extra monitoring to keep TSM from > > crashing. It should just work. Like it did when we were running 5.3... > > Kind regards, > > Eric van Loon > > KLM Royal Dutch Airlines > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of > > Richard Rhodes > > Sent: donderdag 12 mei 2011 15:04 > > To: ADSM-L@VM.MARIST.EDU > > Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code > > > > I have a cron job that checks log utilization every 15m. If the log > > goes > > over 90% the scripts displays a bunch of stuff (q sess, q proc, q log, > > show logpin, etc), runs a show logpin cancel, displays the stuff > > again, > > and finally emails me. (We run in normal mode.) It's been very > > effective > > in preventing a log full condition. > > > > rick > > > > > > > > > > > > > > From: "Bos, Karel" > > To: ADSM-L@VM.MARIST.EDU > > Date: 05/12/2011 06:11 AM >
Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
Thank you Gentlemen, Much Appreciated! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Schneider, Jim Sent: Monday, May 16, 2011 1:52 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code Answer to rookie question: All files backed up create an entry in the transaction log. When the file backup is complete the entry is eligible to be written to the database. TSM only writes the oldest entry in the transaction log. If a file backup takes a long time it can become the oldest entry in the log. Any new entries for backed-up files are stored in the log until the long-running file backup is complete. This is called log pinning. If the backup for one file takes too long the transaction log can become more than 80% full, at which time TSM slows down its backup process to allow transaction log processing to complete. If the transaction log becomes completely full, TSM processing stops. Hope this helps, Jim Schneider -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Mark Mooney Sent: Monday, May 16, 2011 11:23 AM To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code Rookie Question, What is Log Pinning? -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Loon, EJ van - SPLXO Sent: Monday, May 16, 2011 10:19 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code Hi Richard! > So is 5.5.5.0 also having this issue with the log pinning? Yes. As soon as the log hist 80% TSM starts delaying transactions. In this level a bug was fixed which caused the log to fill too soon after it reached 80%. I'm running 5.5.5.2 and it's still filling to 80% multiple times a night. Kind regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Cheung, Richard Sent: zondag 15 mei 2011 04:02 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code Hi The worry about this is I had a PMR opened for this issue on my servers, which are currently at 5.5.4. I was advised it's a known issue, refer to APAR IC64438, and the recommended fix is to go to 5.5.5.0 So is 5.5.5.0 also having this issue with the log pinning? I also believed this was happening in early versions of TSM v6.. But the later builds are okay - can anyone confirm? Richard Cheung | Server Engineer | Information Systems | Santos Limited Santos Centre | 60 Flinders Street Adelaide SA 5000 Australia Ph +61 8 8116 7125 | 7 Fax +61 8 8116 5073 | richard.che...@santos.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Dave Canan Sent: Saturday, 14 May 2011 1:22 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code Andy Raibeck and I have been monitoring this thread for the past few weeks and have been having numerous discussions about what we need to do to address these problems. In addition, we have noted the many PMRs coming into the IBM support queue, and many of these PMRs are now on my queue. Andy will be assisting me along with other support people as needed. As part of this analysis we will be doing, we have a new questionnaire (titled "Items to Gather for a PMR with Log Pinning Condition for TSM V5") that customers will be filling out that ask several questions regarding your environment. We understand that this involves extra work to gather this information, but there can be many different areas that can cause log pinning conditions, so this information is needed. In addition, there will be a script provided (named serverperf5a.pl) that will help us gather additional data. Both of these will be provided to you by support. When these PMRs are now opened, please make sure that level 1 support adds the keyword LOGPIN55 to the PMR. This will allow Andy and I to quickly find all the PMRs being worked for this issue. Eric, your PMR is now one that I have on my queue (or I will shortly today). We will be contacting you to work the PMR. Dave Canan IBM ATS TSM Performance ddcananATUSDOTIBMDOTCOM 916-723-2410 On Thu, May 12, 2011 at 7:53 AM, Loon, EJ van - SPLXO wrote: > Hi Rick! > You are running in normal mode. In this mode the recovery log only > contains uncommited transactions. Don't you agree that in this case, > the log should NEVER reach 90%? It should not even reach something like 40%! > I don't want to have to implement extra monitoring to keep TSM from > crashing. It should just work. Like it did when we were running 5.3... > Kind regards, > Eric van Loon > KLM Royal Dutch Airlines > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of Richard Rho
Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
Wanda, Apologies if this was already mentioned (I haven't read this entire thread), but Expiration can have a dramatic impact when the log is pinned. It does not in itself typically pin the log for long periods of time. However, it can exacerbate the situation where the log is pinned, especially when you have logmode=rollforward. The log is actually circular and has a "head" and a "tail". The oldest open transaction pins the "tail" of the log. Any other updates, whether they remain open or not (for rollforward) will move the "head" forward. When the "head" catches up to the "tail", then the log utilization reaches 100%. The faster the head moves in a situation where the tail is pinned, the faster your log utilization will near 100%. Expiration is one thing which can move the head the fastest (IMHO). When I see our logutil rising, the first thing I check is to see if expiration is running, and if so cancel it. This will slow down the rate of increase in logutil. It would be nice if this happened automatically, even before db writes are slowed down, but I don't believe it does. This may not apply for logmode=normal, I'm not really sure. ..Paul At 04:17 PM 5/15/2011, Prather, Wanda wrote: >Am I correct that scheduling of background processes is important as well? >Don't expiration, migration, backup stgpool also create log transactions? >I'm wondering if it is the housekeeping, rather than the number of client >backups, that is sending my server over the edge. -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: p...@cornell.edu
Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
>>> Andrew Raibeck 5/16/2011 2:04 PM >>> >>Some things that can pin the recovery log: >> >>- NDMP backups that span more than one tape (the pin occurs at the time the >>first tape starts to rewind and another tape is needed) At what point does the NDMP induced pinning get released?
Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
> At what point does the NDMP induced pinning get released? With NDMP, each file system is backed up as an image. Therefore each file system is backed up in its own transaction. The transaction is committed (pin released) when the backup for the file system completes. If the backup does not span more than one tape then there is no pin for the backup of that file system. Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager "ADSM: Dist Stor Manager" wrote on 2011-05-16 15:53:31: > From: David E Ehresman > To: ADSM-L@vm.marist.edu > Date: 2011-05-16 15:59 > Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code > Sent by: "ADSM: Dist Stor Manager" > > >>> Andrew Raibeck 5/16/2011 2:04 PM >>> > >>Some things that can pin the recovery log: > >> > >>- NDMP backups that span more than one tape (the pin occurs at the > time the > >>first tape starts to rewind and another tape is needed) > At what point does the NDMP induced pinning get released?
Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
- Data Protection for * products, typically with large transactions that pin the log until the transaction is committed I'm assuming that a "transaction" for MSSQL = 1 data base when doing the requisite full dump yes? So in the case of ginormous SQL data bases that take hours to back up, what do you recommend to avoid log pinning? -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Andrew Raibeck Sent: Monday, May 16, 2011 2:04 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code Hi Eric (and others following this thread), Just to clarify: we are not aware of any code defects in the TSM 5.5.5 server that would contribute to recovery log pin situations. Rather, it is likely related to workload. But having said that, we do not dismiss any possibility out of hand. Some things that can pin the recovery log: - Windows 2008, Windows 2008 R2, Windows 7 and Windows Vista system state backups using the 6.2 client can cause the recovery log to pin during the object assignment phase of the backup - NDMP backups that span more than one tape (the pin occurs at the time the first tape starts to rewind and another tape is needed) - BACKUP IMAGE operations that span more than one tape (similar situation as NDMP) - Data Protection for * products, typically with large transactions that pin the log until the transaction is committed Of course there can be other reasons as well. It may very well be that others who responds "me too" to this post, could be experiencing the recovery log pin for different reasons. Or we might actually uncover a code-related issue... it all remains to be determined. Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager "ADSM: Dist Stor Manager" wrote on 2011-05-16 10:14:15: > From: "Loon, EJ van - SPLXO" > To: ADSM-L@vm.marist.edu > Date: 2011-05-16 13:13 > Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code > Sent by: "ADSM: Dist Stor Manager" > > Hi Dave! > Thank you VERY VERY much for your help > I'm indeed contacted by your colleague, I filled the document and the > script is currently collecting data. I'm absolutely willing to do the > extra work, if it helps IBM fixing this issue, no problem! > Thanks again! > Kind regards, > Eric van Loon > KLM Royal Dutch Airlines > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of Dave Canan > Sent: vrijdag 13 mei 2011 17:52 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code > > Andy Raibeck and I have been monitoring this thread for the past few > weeks and have been having numerous discussions about what we need to > do to address these problems. In addition, we have noted the many PMRs > coming into the IBM support queue, and many of these PMRs are now on > my queue. Andy will be assisting me along with other support people as > needed. > > As part of this analysis we will be doing, we have a new questionnaire > (titled "Items to Gather for a PMR with Log Pinning Condition for TSM > V5") > that customers will be filling out that ask several questions > regarding your environment. We understand that this involves extra > work to gather this information, but there can be many different areas > that can cause log pinning conditions, so this information is needed. > In addition, there will be a script provided (named serverperf5a.pl) > that will help us gather additional data. Both of these will be > provided to you by support. When these PMRs are now opened, please > make sure that level 1 support adds the keyword LOGPIN55 to the PMR. > This will allow Andy and I to quickly find all the PMRs being worked > for this issue. > > Eric, your PMR is now one that I have on my queue (or I will shortly > today). > We will be contacting you to work the PMR. > > Dave Canan > IBM ATS TSM Performance > ddcananATUSDOTIBMDOTCOM > 916-723-2410 > > On Thu, May 12, 2011 at 7:53 AM, Loon, EJ van - SPLXO > > wrote: > > > Hi Rick! > > You are running in normal mode. In this mode the recovery log only > > contains uncommited transactions. Don't you agree that in this case, > the > > log should NEVER reach 90%? It should not even reach something like > 40%! > > I don't want to have to implement extra monitoring to keep TSM from > > crashing. It should just work. Like it did when we were running 5.3... > > Kind regards, > > Eric van Loon > > KLM Royal Dutch Airlines > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > > Behalf > Of > > Richard Rhodes > > Sent:
Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
With Oracle TDP we are able to set the chunk/transaction size. By default it tries to do a whole database as a single transaction. We broke up the problem nodes into 2GB chunks. "Prather, Wanda" wrote: - Data Protection for * products, typically with large transactions that pin the log until the transaction is committed I'm assuming that a "transaction" for MSSQL = 1 data base when doing the requisite full dump yes? So in the case of ginormous SQL data bases that take hours to back up, what do you recommend to avoid log pinning? -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Andrew Raibeck Sent: Monday, May 16, 2011 2:04 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code Hi Eric (and others following this thread), Just to clarify: we are not aware of any code defects in the TSM 5.5.5 server that would contribute to recovery log pin situations. Rather, it is likely related to workload. But having said that, we do not dismiss any possibility out of hand. Some things that can pin the recovery log: - Windows 2008, Windows 2008 R2, Windows 7 and Windows Vista system state backups using the 6.2 client can cause the recovery log to pin during the object assignment phase of the backup - NDMP backups that span more than one tape (the pin occurs at the time the first tape starts to rewind and another tape is needed) - BACKUP IMAGE operations that span more than one tape (similar situation as NDMP) - Data Protection for * products, typically with large transactions that pin the log until the transaction is committed Of course there can be other reasons as well. It may very well be that others who responds "me too" to this post, could be experiencing the recovery log pin for different reasons. Or we might actually uncover a code-related issue... it all remains to be determined. Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager "ADSM: Dist Stor Manager" wrote on 2011-05-16 10:14:15: > From: "Loon, EJ van - SPLXO" > To: ADSM-L@vm.marist.edu > Date: 2011-05-16 13:13 > Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code > Sent by: "ADSM: Dist Stor Manager" > > Hi Dave! > Thank you VERY VERY much for your help > I'm indeed contacted by your colleague, I filled the document and the > script is currently collecting data. I'm absolutely willing to do the > extra work, if it helps IBM fixing this issue, no problem! > Thanks again! > Kind regards, > Eric van Loon > KLM Royal Dutch Airlines > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of Dave Canan > Sent: vrijdag 13 mei 2011 17:52 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code > > Andy Raibeck and I have been monitoring this thread for the past few > weeks and have been having numerous discussions about what we need to > do to address these problems. In addition, we have noted the many PMRs > coming into the IBM support queue, and many of these PMRs are now on > my queue. Andy will be assisting me along with other support people as > needed. > > As part of this analysis we will be doing, we have a new questionnaire > (titled "Items to Gather for a PMR with Log Pinning Condition for TSM > V5") > that customers will be filling out that ask several questions > regarding your environment. We understand that this involves extra > work to gather this information, but there can be many different areas > that can cause log pinning conditions, so this information is needed. > In addition, there will be a script provided (named serverperf5a.pl) > that will help us gather additional data. Both of these will be > provided to you by support. When these PMRs are now opened, please > make sure that level 1 support adds the keyword LOGPIN55 to the PMR. > This will allow Andy and I to quickly find all the PMRs being worked > for this issue. > > Eric, your PMR is now one that I have on my queue (or I will shortly > today). > We will be contacting you to work the PMR. > > Dave Canan > IBM ATS TSM Performance > ddcananATUSDOTIBMDOTCOM > 916-723-2410 > > On Thu, May 12, 2011 at 7:53 AM, Loon, EJ van - SPLXO > > wrote: > > > Hi Rick! > > You are running in normal mode. In this mode the recovery log only > > contains uncommited transactions. Don't you agree that in this case, > the > > log should NEVER reach 90%? It should not even reach something like > 40%! > > I don't want to have to implement extra monitoring to keep TSM from > > crashing. It should just work. Like it did when we were running 5.3...
