Kbase P137502: SQL clients cannot connect to database even though there are enough servers available.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
27/04/2010 |
|
Status: Verified
SYMPTOM(s):
SQL clients cannot connect to database even though there are SQL servers available.
Cannot connect to a database using ODBC test connect due to error 8839
No SQL servers are available. Try again later. (8839)
Broker rejected connection
SQL servers are spawned but appear to have users already connected even though no users are actually connected to them
promon shows that _sqlsrv2 processes have user(s) connected according to the Current user column, even though no users are actually connected to that server process.
FACT(s) (Environment):
Previous clients connected to these servers logged out successfully.
Logout by <user> on <ttyxxx>. (453)
4GL users can connect to the database just fine.
Error occurs for regular user and sysprogress user.
Terminating the _sqlsrv2 process results in new _sqlsrv2 process being spawned upon next connection attempt.
Users connecting to the new _sqlsrv2 processes are able to disconnect and have the user count in promon decrement appropriately.
Multiple database brokers being used.
Windows
OpenEdge 10.0B
OpenEdge 10.1B
OpenEdge 10.1C
OpenEdge 10.2A
UNIX
CAUSE:
Bug# OE00175214
FIX:
Upgrade to 10.1C03.
Upgrade to 10.2A01.
Workaround for this issue is to validate that there are no remote users connected to the specific _sqlsrv2 process. Then terminate the process. The next remote ODBC or JDBC client that attempts to connect to the database will result in the broker spawning a new _sqlsrv2 process. The clients will then be able to connect to the newly spawned _sqlsrv2 process. See solution: P39432, "Is it possible to trim _mprosrv and _sqlsrv2 processes?" for additional information on how to use promon to terminate server processes.