Unable to access proutil when DB online

Manohar

New Member
How did you start the database? Please be specific.
Using start up script -
The contents are -

DLC=/progress/v10/dlc10.1c;export DLC
PATH=$PATH:$DLC;export PATH
PROMSGS=$DLC/promsgs;export PROMSGS
PROTERMCAP=$DLC/protermcap;export PROTERMCAP
PROCFG=$DLC/progress.cfg;export PROCFG
$DLC/bin/proutil /crlive/crlive08 -C EnableLargeFiles
$DLC/bin/_mprosrv /crlive/crlive08 -L 200000 -c 350 -B 20000 -n 235 -semsets 10 -S crmfglive -N TCP -Mn 10
$DLC/bin/_mprosrv /crlive/crhlp08 -L 100000 -c 350 -B 1000 -n 235 -semsets 10 -S crhlplive -N TCP -Mn 10
$DLC/bin/proutil /crlive/crlive08 -C EnableLargeFiles
$DLC/bin/_mprosrv /crlive/cradm08 -L 100000 -c 350 -B 10000 -n 235 -semsets 10 -S cradmlive -N TCP -Mn 10
$DLC/bin/_mprosrv /crlive/tnmfgpro -L 100000 -c 350 -B 5000 -n 235 -semsets 10 -S crtnmlive -N TCP -Mn 10
$DLC/bin/_mprosrv /crlive/qxevents -L 50000 -c 350 -B 5000 -n 235 -semsets 10 -S crqxtlive -N TCP -Mn 10


This is live environment and accessible to users now.
 

Rob Fitzpatrick

ProgressTalk.com Sponsor
Using start up script -
The contents are -

DLC=/progress/v10/dlc10.1c;export DLC
PATH=$PATH:$DLC;export PATH
PROMSGS=$DLC/promsgs;export PROMSGS
PROTERMCAP=$DLC/protermcap;export PROTERMCAP
PROCFG=$DLC/progress.cfg;export PROCFG
$DLC/bin/proutil /crlive/crlive08 -C EnableLargeFiles
$DLC/bin/_mprosrv /crlive/crlive08 -L 200000 -c 350 -B 20000 -n 235 -semsets 10 -S crmfglive -N TCP -Mn 10
$DLC/bin/_mprosrv /crlive/crhlp08 -L 100000 -c 350 -B 1000 -n 235 -semsets 10 -S crhlplive -N TCP -Mn 10
$DLC/bin/proutil /crlive/crlive08 -C EnableLargeFiles
$DLC/bin/_mprosrv /crlive/cradm08 -L 100000 -c 350 -B 10000 -n 235 -semsets 10 -S cradmlive -N TCP -Mn 10
$DLC/bin/_mprosrv /crlive/tnmfgpro -L 100000 -c 350 -B 5000 -n 235 -semsets 10 -S crtnmlive -N TCP -Mn 10
$DLC/bin/_mprosrv /crlive/qxevents -L 50000 -c 350 -B 5000 -n 235 -semsets 10 -S crqxtlive -N TCP -Mn 10


This is live environment and accessible to users now.
The proper way to configure your OE version in the shell is to set the DLC directory, then add $DLC/bin to the beginning of the PATH, and then export both DLC and PATH.

In the subshell of your DB start script, you set and export DLC and then you add $DLC to the end of the PATH. You don't add $DLC/bin at all. It should look like this:
Code:
DLC=/progress/v10/dlc10.1c;export DLC
PATH=$DLC/bin:$PATH;export PATH

The proutil commands don't belong in your DB start script. Enabling large file support is something you do to a database once in its lifetime. So your first proutil command is being ignored because that feature has already been enabled. Your second proutil command is being ignored because the database has already been started at that point and that command is not allowed to run against an online database.

Try making those changes and then restart your databases.
 

TomBascom

Curmudgeon
In practice _proutil is often different but it calls _dbutil to do a lot of the dirty work. It is _dbutil and _mprosrv that I would expect should have identical time stamps.

If that is what is going on here and you have a different server that works correctly (and where the time stamps match) I would think that someone manually copied some, but not all, of the relevant executables at some point.

Or… they applied a service pack with stuff running and part of that update failed resulting in an out of sync install.

To fix it you need to reinstall or reapply the service pack or copy an existing (and working) install. Make sure everything from Progress is shutdown first. And make backups of course.

FWIW on Unix systems the usual process is to leave the existing install in place and to create a new, fresh directory. Then use DLC and PATH to point at the new stuff. This way you can test the new stuff without disturbing anything that other people are working with and migrate at your leisure.

You should also upgrade to a supported version of Progress.
 
Top