Kbase 19044: Exceeding Permissible Number of Connections: SQL-92
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
08/01/2002 |
|
SUMMARY:
This solution applies to the Progress SQL-92 Engine Version 9.0B and later.
An ODBC/JAVA/ESQLC client might get the following error at connection time even though all users licenses are not used:
As displayed in Version 9.0B:
Exceeding permissible number of connections
As displayed in Version 9.1A:
SQL Error State: S1000, Native Error Code: FFFFBOFF,
ODBC Error:
[MERANT][ODBC PROGRESS driver][PROGRESS] Exceeding
permissible number of connections.
EXPLANATION:
Generally, when a client requests a connection to the Progress broker, a server is spawned to serve that particular client. The same broker is able to spawn both the 4GL server to serve 4GL clients and SQL Server to serve ODBC/JAVA/ESQLC clients.
Unlike the 4GL server, SQL Server can serve a maximum of one (1)
ODBC/JAVA/ESQLC client. The parameter -Mn specifies to the broker the maximum number of servers (SQL Server + 4GL Server) that can be spawned.
The error can appear if the broker is unable to spawn the server due to the setting of the -Mn parameter.
For example:
Assume that you have 20 users licenses.
1) Start your database as follows:
proserve <dbname> -S <portnumber> -n 20 -Mn 4 -Ma 5
2) Make five ODBC/JAVA/ESQLC connections into the database.
The first four(4) connections should be okay, but the 5th
receives the error. This is caused partly because the -Mn
parameter is set to 4, but it could also be because the "1
SQL Server = 1 ODBC/JAVA/ESQLC client".
SOLUTION:
If you disconnect all ODBC/JAVA/ESQLC clients, 20 4GL clients can
connect into the database. Increase the database parameter -Mn in order to allow more ODBC/JAVA/ESQLC connections.
Reference to Written Documentation:
System Administration Reference.
SQL-92 Guide and Reference.