one of our customers has problems with ASE 11.9.2 on Solaris 5.6.
He gets the error 1204, server log:
02:00000:00006:2002/06/07 15:29:23.69 server Error: 1204, Severity: 17, State: 2
02:00000:00006:2002/06/07 15:29:23.69 server SQL Server has run out of LOCKS.
Re-run your command when there are fewer active users, or contact a user with Sy
stem Administrator (SA) role to reconfigure SQL Server with more LOCKS.
But he has set the "number of locks" up to 2 million and still gets
this error. Other customers don't get this error with values like
5000 (default) or 7500.
Does anyone have an idea ?
Jürgen Bajdala
> He gets the error 1204, server log:
> 02:00000:00006:2002/06/07 15:29:23.69 server Error: 1204, Severity: 17, State: 2
> 02:00000:00006:2002/06/07 15:29:23.69 server SQL Server has run out of LOCKS.
> Re-run your command when there are fewer active users, or contact a user with Sy
> stem Administrator (SA) role to reconfigure SQL Server with more LOCKS.
>
> But he has set the "number of locks" up to 2 million and still gets
> this error. Other customers don't get this error with values like
> 5000 (default) or 7500.
>
> Does anyone have an idea ?
Select from master..syslocks to see what table is running up the
locks and look at his query.
-am © 2002
1- Tables that have row-level locking
2- tcp_keepalive OS configuration parameter..set it to 2-3 minutes
3- lock promotion configuration parameters
4- number of Simultaneous connections using same tables..
5- table level fragmentation..check out the cluster ratios using optdiag..
"J. Bajdala" <b...@sisis.de> wrote in message news:<3D05A5B0...@sisis.de>...
Is he using row-level locking on any tables?
If so, any large-scale activity on tables with many rows?
You might consider doing some monitoring of lock usage by scheduling
a regular "select * from syslocks" into a file; this will show you number
of locks used at variousl points and if any particular objects are getting
unusually large numbers of locks.
-bret