Kbase 21848: "Database not started" When Attempting SQL92/ODBC Connection
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
28/02/2002 |
|
SUMMARY:
The following error might be seen on Windows 32-bit client machines when you attempt to make a SQL-92/ODBC connection to a Progress 9.1x database:
[MERANT][ODBC Progress Driver][Progress] Database not started.
Meanwhile, error 8841 is reported to the Progress database log file:
SQL server process terminated. (8841)
EXPLANATION:
The (8841) message occurs because the SQL-92 server process (_sqlsrv2) cannot be automatically spawned by the database broker. This might be due to the UNIX permissions set on the _sqlsrv2 executable itself. Often, Progress users set the permissions on all their Progress executables (contained within the $DLC/bin directory) to 4755, thus the SUID bit is set on all these files. In some cases, if the SUID bit is set on both the Progress database broker executable (_mprosrv) and the SQL-92 server executable (_sqlsrv2) the SQL-92 server process won't start.
SOLUTION:
To resolve the problem, try setting the UNIX permissions on the Progress SQL-92 server executable (_sqlsrv2) to 755.
Meanwhile, leave the Progress database broker executable (_mprosrv) set to 4775. The files should then appear as follows:
-rwsrwxr-x 1 root rdl 1693006 Jun 6 2001 _mprosrv
-rwxr-xr-x 1 ccall rdl 595654 Jun 6 2001 _sqlsrv2
References to Written Documentation:
Progress Knowledge Base Solution 21552, "Progress SQL-92 Server -- Common Issues and How To Avoid Them"