Consultor Eletrônico



Kbase P31752: Not setting shared library path environment variables can cause ODBC client not to connect
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   15/06/2005
Status: Verified

FACT(s) (Environment):

UNIX
Windows 2000
Progress 9.1D

SYMPTOM(s):

Can not connect to database from ODBC

[DataDirect-Technologies][ODBC PROGRESS driver][PROGRESS]Database not started

Error received from test connect

Connecting from Windows client to database on UNIX

CAUSE:

Database had been started with the $DLC/bin/_mprosrv executable rather than with the $DLC/bin/proserve script. The proserve script not only calls the _mprosrv executable, but also sets some required environment variables for loading shared libraries.

FIX:

Start the database with the proserve script, or if using _mprosrv, make sure $DLC/bin/slib_env is run prior to starting _mprosrv
Using _mprosrv is ok if only 4GL clients are going to connect. 4GL clients will not require java to run.
For SQL/Java clients, however, proserve should be used because it sets up the java environment.