• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2871
  • Last Modified:

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
0
virgo0880
Asked:
virgo0880
  • 4
  • 3
1 Solution
 
max_the_kingCommented:
Hi,
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
0
 
virgo0880Author Commented:
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
0
 
max_the_kingCommented:
Hi,
by script tuning i meant that you should check when and how the backup db, backup stgpool, expire inventory, etc. are happening ... but now i'm getting the idea that the problem resides in the backup process by your mail server. It may well be that it is running very slowly or it hangs. I'd give a deep inspection at that backup process, by reading the client log and see if there is something to fix.
You  may want to read the following IBM document: http://publib.boulder.ibm.com/tividd/td/TSMM/SC32-9103-01/en_US/HTML/srv_log.html

I'm pasting the part you should investigate:
**********************************************************************
Out of recovery log space

Issue QUERY LOG. If the "Pct. Util" is very high, such as close to 100%, the server will report out of recovery log space during operations that need to add or change database information.

You can take a number of steps to provide more recovery log space.

    If the "Maximum Extension" value reported by the QUERY LOG command is greater than zero, issue EXTEND LOG nn where nn is the available space that the recovery log can be extended as reported by QUERY LOG.
    Define additional recovery log volumes using the DEFINE LOGVOLUME command. After defining one or more additional recovery log volumes, issue QUERY LOG and extend the recovery log by all or some of the available extension amount using EXTEND LOG nn where nn is the extension amount.
    If the server crashed because it was out of recovery log space and fails to start, it may be necessary to do an emergency extend of the recovery log. This is done by issuing DSMSERV EXTEND LOG volumeName amount where volumeName is a formatted recovery log volume and amount is the amount (in megabytes) to extend the recovery log.

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.

It is possible that the recovery log appears to be out of space when in fact it is being pinned by an operation or combination of operations on the server. A pinned recovery log is where space in the recovery log can not be reclaimed and used by current transactions because an existing transaction is processing too slowly or is hung. To determine if the recovery log is pinned, issue SHOW LOGPINNED repeatedly over many minutes. If this reports the same client session or server processes as pinning the recovery log, it may be necessary to take action to cancel or terminate that operation in order to keep the recovery log from running out of space. To cancel or terminate a session or process that is pinning the recovery log, issue SHOW LOGPINNED CANCEL. Server version 5.1.7.0 and above as well as 5.2.0.0 and above have additional support for the recovery log to automatically recognize that the recovery log is running out of space and where possible to detect and resolve a pinned recovery log using the SHOW LOGPINNED processing.
*************************************************************************

hope this helps
max
0
 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

 
virgo0880Author Commented:
Thanks max, I will go through the link.
0
 
virgo0880Author Commented:
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
0
 
max_the_kingCommented:
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
0
 
virgo0880Author Commented:
Yes  Max, I am aware of that. Thanks for your help.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now