max connections with sql92 and 9.1b database

[egiblock]

we just migrated our database from unix to windows.

we also have a handful of people that connect to it with access using the merant 3.60 sql92 odbc driver.

we have been getting a exceeding maximum number of possible connections when more than one person gets into the database using a duplicate odbc login name like 'administrator' or 'public'. but it also seems after X amount of people are in the database.

looking at the database locks viewer i get the following:
** i changed the user names to 'userlogX' **


Locking and Waiting:
Type Usr Name Record Trans Schema
Lock 999 TOTAL... 8628798 14930 11
Wait 999 TOTAL... 0 0 36
Lock 0 Administ 0 0 0
Wait 0 Administ 0 0 0
Lock 1 Administ 0 0 0
Wait 1 Administ 0 0 0
Lock 2 Administ 0 0 0
Wait 2 Administ 0 0 0
Lock 3 Administ 0 0 0
Wait 3 Administ 0 0 0
Lock 4 Administ 0 0 0
Wait 4 Administ 0 0 0
Lock 5 Administ 0 0 0
Wait 5 Administ 0 0 0
Lock 6 Administ 0 0 0
Wait 6 Administ 0 0 0
Lock 7 Administ 0 0 0
Wait 7 Administ 0 0 0
Lock 8 0 0 0
Wait 8 0 0 0
Lock 9 0 0 0
Wait 9 0 0 0
Lock 10 0 0 0
Wait 10 0 0 0
Lock 11 administ 0 0 0
Wait 11 administ 0 0 0
Lock 204 administ 3 0 0
Wait 204 administ 0 0 0
Lock 205 userlog1 1539 0 0
Wait 205 userlog1 0 0 0
Lock 206 userlog2 14374 532 0
Wait 206 userlog2 0 0 0
Lock 207 userlog3 57 0 0
Wait 207 userlog3 0 0 0


any idea of what we are doing wrong here ?

any other information that is needed, i can post here.

thanks


** i've attached screen shots of the error messages we get in access.

 

[Casper]

we just migrated our database from unix to windows.

You had to do a dump load for that. You missed out the perfect chance of making use of type II storage area's and a new version of Progress like 10.1C or 10.2A.... (This also would have given you much much much better sql access to the database).

exceeding maximum number of possible connections.

This means the _sqlsrv2 proces which handles the sql connection hasn't got a free server anymore.
If you don;t use a dedicated broker for your sql connections then do so. If you do, check for the settings of -Ma and -Mpb for your sql broker. -Ma * -Mpb is the number of possible connections.

You best check server availibility on a database through the promon R&D 1, 3 option. There you can see how many connections there are. If the queries are not good then you could also experience hanging connections which can cause your _sqlsrv2 servers to become unresponsive. Killing the servers or restarting the database will be the only option you have then. NOTE: You can only kill a server if you are certain there are no active transactions on that server.

HTH,

Casper.