Kbase P124606: Cannot start database with proserve
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/29/2008 |
|
Status: Verified
SYMPTOM(s):
Cannot start database with proserve
4098 Memory fault(coredump)
4351 Memory fault(coredump)
Many 1423 8619 error messages in quick succession
There is no server for database <dbname>. (1423)
** This process terminated with exit code 2. (8619)
Database starts with _mprosrv
FACT(s) (Environment):
Other progress scripts like: proshut work as expected
There are more than one Progress version installed on the server
Applications run under each version of Progress installed
/usr/bin does not contain 'other' versions of progress executables
The progress install was not copied from another server
The proserve script is called from a custom script
The proserve script has not been modified
The proserve script is not corrupt
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
CHANGE:
Starting database with proserve instead of _mprosrv
CAUSE:
The difference between calling _mprosrv and proserve, is that the first is the executable (direct) and the second is a shell script that calls the _mprosrv executable. As such if the environment variables are not being called appropriately, this situation can arise.
FIX:
Contrary to popular opinion, it is not an absolute requirement to start the database with the 'proserve' executable when needing to make ODBC connections to the database. The existing scripts can be modified to include the following, (to set the java environment) before calling the _mprosrv to start the database:
. $DLC/bin/slib_env
. $DLC/bin/java_env
Otherwise a script de-bugging exercise needs to be undertaken.