August 4, 2009 at 5:06 am
Hi Guys,
We have recently implemented IBM Tivoli Monitoring tool to alert the events from some of our SQL Server DB Instances.
There were a number of alerts in the list and I have selected around 50 of them to monitor on a daily basis which includes the MS_SQL_PCT_MAX_Locks_Critial (>=80%) & MS_SQL_PCT_MAX_Locks_Warning (60%-80%)
I got an alert over the weekend at 01/08/2009 04:13 as follows,[There will not be any business users using the system at the above mentioned time]
I have SQL Server 2000 Sp4 running on Windows 2003 server.
PRSQL01 MS_SQL_PCT_MAX_Locks_Critical[(Percent_Max_Locks>=80.00 ) ON PRSQL01:PRSQL01:MSS (Percent_Max_Locks=502.98 )]
At the moment the DB server is perfect and fully functional with out any problems.
I know SQL Server will prevent users from logging on if the maximum number of configured locks is reached which could potentially hang the system.
Can anyone tell me how to find the max number of configured locks?
How to manage this parameter?
Is there anyone out there found any e-books with the details on these parameters and possible solutions?
Thanks,
Philip.
August 4, 2009 at 7:19 am
Philip (8/4/2009)
How to manage this parameter?
sp_configure
Philip (8/4/2009)
Is there anyone out there found any e-books with the details on these parameters and possible solutions?
BOL
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.August 4, 2009 at 9:56 am
Hi Paul,
I ran sp_configure but received the following,
locks5000214748364700
which is not of any help in co-relating the alert to the parameter based on the numbers mentioned in the error,
I have searched for the site books online (BOL?) but no reference of Tivoli!
Thanks,
Philip.
August 4, 2009 at 10:26 am
did you check BOL? you will see that the config_value of 0 means self managed. So your max is the server instance maximum.
Also -- this looks interesting:
PRSQL01 MS_SQL_PCT_MAX_Locks_Critical[(Percent_Max_Locks>=80.00 ) ON PRSQL01:PRSQL01:MSS (Percent_Max_Locks=502.98 )]
Percent is greater than 80% -- OK
actual value = 502.98% ?????
I'd guess Tivoli is doing it's own calculation?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply