DBTool fails with juMsgProcessInit error

por | 1 marzo, 2015

Short answer

run dbtool with sudo,root, or admin privileges, it has to access shared memory


Article Number 000010823
Environment Progress 9.1E
OpenEdge 10.x
All Supported Operating Systems
Question/Problem Description
DBTool fails with juMsgProcessInit error
juMsgProcessInit failed 1
juMsgProcessInit failed 1
ERROR connecting 1
Clarifying Information
Error Message
Defect/Enhancement Number
This message is returned when the dbtool fails to connect to the database.  «juMsgProcessInit failed 1» error is returned when the database lg file and/or the promsgs file cannot be accessed by the utility.
Before running dbtool, ensure that the environment is properly set where the dbtool utility is started:- as user who has access to database (ie root)
– in the directory where the database.db is found, hence the dbname.lg file
– the $DLC $PROPATH and $PATH environment variables are set to the Progress install. The shared memory version for dbtool must match the database, ie: same version. There is no Client-Server connection option for dbtool.

When using the option:
<connect>: (0=single-user 1=self-service >1=#threads)? 0
implies a single-user connection to the database, so the database must not be running. This method is recommended when running «fix» options.

For example:
Option 2. SQL Width Scan w/Fix
ie: fixing while database is off line against specific table/areas reported as needing the SQL Width adjusting from (say) a previous full scan report with threading: «1. SQL Width & Date Scan w/Report Option».

When using the option:
<connect>: (0=single-user 1=self-service >1=#threads)? 3
implies that the database is running and the number greater than 0 is the number of threads to use for the utility (= CPU’s). Threaded utilities are only available when the database is running. Otherwise connect with the 0 value for single user, without threading.

Always flag the «9. Enable/Disable File Logging» to create the dbtool.out with the results for future reference.  The statistics of a successful run will report the findings.

For example:
Total records read: 1117
SQLWidth errors found: 5,
Date errors found: 1
SQLWidth errors fixed: 6

The table/fields that these apply to will be marked with a triple asterisk in the report ***

The verbose level above 1 «<display>: (verbose level 0-3)? » should only be selected when there are specific problems needing to be reported to your regional Progress Technical Support.

Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an «AS IS» basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.