This is a discussion on sp_configure locks Configuration option is not unique. within the Sybase forums, part of the Database Server Software category; --> Hi I have a sybase server Version 12.0 running on solaris 5.6 and one user is getting the following ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi I have a sybase server Version 12.0 running on solaris 5.6 and one user is getting the following error message Msg 1204, Level 17, State 2: Server 'TIBET_12DS', Line 105: 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. this is the locks that I have Parameter Name Default Memory Used Config Value Run Value ------------------------------ ----------- ----------- ------------ ----------- max engine freelocks 10 0 10 10 number of locks 5000 1407 10000 10000 Now I don't have that many users connected the max is 40 at times and I don't know what to do... I tryed to increase, and I get this message 1> sp_configure locks, 10000 2> go Msg 17411, Level 16, State 1: Server Procedure 'sp_configure', Line 161: Configuration option is not unique. Parameter Name Default Memory Used Config Value Run Value ------------------------------ ----------- ----------- ------------ ----------- max engine freelocks 10 0 10 10 number of locks 5000 1407 10000 10000 (1 row affected) (return status = 1) 1> I would appreciate any help Thank You Teresa |
| |||
| tpreto7@sapo.pt (Teresa) wrote in news:6dabc692.0308191246.2c061943@posting.google.c om: > 1> sp_configure locks, 10000 > 2> go > Msg 17411, Level 16, State 1: > Server Procedure 'sp_configure', Line 161: > Configuration option is not unique. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is telling you that 'locks' is not a unique configuration option and it shows you the two config options below that map to it: > Parameter Name Default Memory Used Config > Value > Run Value > ------------------------------ ----------- ----------- > ------------ > ----------- > max engine freelocks 10 0 > 10 > 10 > number of locks 5000 1407 > 10000 > 10000 All you have to do is make config more unique. I think that's really what you're asking, ah, of course! <g> okay, what you need to do is: sp_configure "number of locks", 20000 go -- Pablo Sanchez, Blueoak Database Engineering http://www.blueoakdb.com |
| ||||
| tpreto7@sapo.pt (Teresa) wrote in message news:<6dabc692.0308191246.2c061943@posting.google. com>... > Hi > > I have a sybase server Version 12.0 running on solaris 5.6 and one > user is getting the following error message > Msg 1204, Level 17, State 2: > Server 'TIBET_12DS', Line 105: > 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. > > > this is the locks that I have > > Parameter Name Default Memory Used Config Value > Run Value > ------------------------------ ----------- ----------- ------------ > ----------- > max engine freelocks 10 0 10 > 10 > number of locks 5000 1407 10000 > 10000 > > > Now I don't have that many users connected the max is 40 at times and > I don't know what to do... I tryed to increase, and I get this message > > 1> sp_configure locks, 10000 > 2> go > Msg 17411, Level 16, State 1: > Server Procedure 'sp_configure', Line 161: > Configuration option is not unique. > > Parameter Name Default Memory Used Config Value > Run Value > ------------------------------ ----------- ----------- ------------ > ----------- > max engine freelocks 10 0 10 > 10 > number of locks 5000 1407 10000 > 10000 > > (1 row affected) > (return status = 1) > 1> > > I would appreciate any help > > Thank You > Teresa The string "locks" occurs in both of the listed configuration parameter names, ASE doesn't know which one you mean. Try sp_configure "number of locks", 15000 go instead (I increased the value as you were already at 10000 locks). -bret |