virgo0880
asked on
TSM log utilization threshold exceeded
Hi All,
yesterday, our TSM server throwed alert saying TSM log utilization threshold exceeded and all the sessions got hung. when I saw, one of our mailbox server was pinning the log. I issued logpin cancel but no success. This has happened twice or thrice now and I have to take a reboot of TSM services to resume normal operations. there are various threads on google suggesting some recommendations. So, here I want to know that whether I should increase the size of my recovery log volume or what option should I put in logmode - whether normal or rollover. As of now we are having normal, also the size of recovery log is 8GB. I need some suggestions on this and how this problem can be resolved ? Following is the output of my q log command:
Available Space (MB): 8,192
Assigned Capacity (MB): 8,192
Maximum Extension (MB): 0
Maximum Reduction (MB): 8,184
Page Size (bytes): 4,096
Total Usable Pages: 2,096,640
Used Pages: 466
Pct Util: 0.0
Max. Pct Util: 11.0
Physical Volumes: 2
Log Pool Pages: 1,024
Log Pool Pct. Util: 0.82
Log Pool Pct. Wait: 0.00
Cumulative Consumption (MB): -5,869,240.75
Consumption Reset Date/Time: 12/20/06 18:57:58
Thanks
virgo
yesterday, our TSM server throwed alert saying TSM log utilization threshold exceeded and all the sessions got hung. when I saw, one of our mailbox server was pinning the log. I issued logpin cancel but no success. This has happened twice or thrice now and I have to take a reboot of TSM services to resume normal operations. there are various threads on google suggesting some recommendations. So, here I want to know that whether I should increase the size of my recovery log volume or what option should I put in logmode - whether normal or rollover. As of now we are having normal, also the size of recovery log is 8GB. I need some suggestions on this and how this problem can be resolved ? Following is the output of my q log command:
Available Space (MB): 8,192
Assigned Capacity (MB): 8,192
Maximum Extension (MB): 0
Maximum Reduction (MB): 8,184
Page Size (bytes): 4,096
Total Usable Pages: 2,096,640
Used Pages: 466
Pct Util: 0.0
Max. Pct Util: 11.0
Physical Volumes: 2
Log Pool Pages: 1,024
Log Pool Pct. Util: 0.82
Log Pool Pct. Wait: 0.00
Cumulative Consumption (MB): -5,869,240.75
Consumption Reset Date/Time: 12/20/06 18:57:58
Thanks
virgo
ASKER
I am running full DB backup daily once but even though it log pining happens. Now, it happened just yesterday and i have to take a reboot of the TSM services to resume normal operations. I will try to take the db backup if this happens again.
Also, what maintenance script tuning you are talking about here?
virgo
Also, what maintenance script tuning you are talking about here?
virgo
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks max, I will go through the link.
ASKER
I called IBM Tivoli support and they told me to increase the size of the recovery log volume to 12GB. After doing this, I have not faced log pinning issues so far.
Thanks
virgo
Thanks
virgo
Fine !
Please note that you have just reached the limit, as I mentioned in previous note:
"The recovery log has a maximum size of 13GB. It is recommended that the recovery log only be defined or extended to 12GB so that there is 1GB in reserve if you need to do an emergency extend needs to be done. In the event that an emergency extend is done, reduce the recovery log after restarting the server to preserve the 1GB reserve amount."
Keep an eye to its utilization "q log F=D" every now and then
You can as well monitor it by issuing the following query:
Q ACTL BEGINDATE=-7 SEARCH=ANR2997W
which will give you the occurrence of a log increasing more than 80% in the last 7 days.
max
Please note that you have just reached the limit, as I mentioned in previous note:
"The recovery log has a maximum size of 13GB. It is recommended that the recovery log only be defined or extended to 12GB so that there is 1GB in reserve if you need to do an emergency extend needs to be done. In the event that an emergency extend is done, reduce the recovery log after restarting the server to preserve the 1GB reserve amount."
Keep an eye to its utilization "q log F=D" every now and then
You can as well monitor it by issuing the following query:
Q ACTL BEGINDATE=-7 SEARCH=ANR2997W
which will give you the occurrence of a log increasing more than 80% in the last 7 days.
max
ASKER
Yes Max, I am aware of that. Thanks for your help.
let me try and answer your questions:
1. "I want to know that whether I should increase the size of my recovery log volume": no, I wouldn't definitely do that, 8 GB is usually enough even for major implementations (and please note that up to TSM 5.5 the max capacity of Log is 13 GB).
2. I'd leave it in Normal mode.
what i suggest is to run full db backup more often. I do not know what you have set now, but as a rule of thumb once a day should be fine. If you still experience this problem, you may want to try and do a db backup right before your mail server starts pinning the log.
I believe that tuning maintenance script will solve your problems
hope this helps
max