Unanswered: SQL Server which has temporarily run out of locks.
we had a problem the other day when, our sybase server 220.127.116.11 locked up.
we got the following errors.
1. Could not obtain required number '3' of resource of type 'Free Locks'. Since the process absolutely requires thi
s resource, it is going to wait indefinitely till the resource becomes available. Please increase the configuration parameter 'number of locks'.
2. SQL Server has run out of LOCKS. Re-run your command when there are fewer active users, or contact a user with
System Administrator (SA) role to reconfigure SQL Server with more LOCKS.
3. An earlier indefinite wait for resource of type 'Free Locks' by this process is over as '3' resources became ava
ilable. Process is continuing further.
We are trying to find out what has happened, are default number of locks in 50000, which is enough.
It means, your queries are taking more number of locks (read about Locking in http://sybooks.sybase.com) than what is configured. Theres no magic number for number of locks. Totally depends on the Application and what you are querying.
It doesnt take too much memory, so you can keep increasing it until you find a right number. If I remember right in 12.0.x the annoying part is its not a dynamic parameter. So you have to bounce the server after