Mws.sh init script failing

1

Product/components used and version/fix level: webMethods 10.15

I am trying to do a fresh installation of webMethods 10.15. So far I have done the following:

  • Made sure that mws can connect to the associated database

  • Verified keystore/truststore certificates and passwords

  • Ran the following dbConfigurator commands, each ran successfully:

./dbConfigurator.sh -a create -d oracle -pr IS -v latest -l $DB_JDBC_URL -u $DB_USR_WEBM -p "$DB_PWD_WEBM" -tsdata WEBMDATA -tsindex WEBMINDX
./dbConfigurator.sh -a create -d oracle -pr MwS -v latest -l $DB_JDBC_URL -u $DB_USR_WEBM -p "$DB_PWD_WEBM" -tsdata WEBMDATA -tsindex WEBMINDX
./dbConfigurator.sh -a create -d oracle -c ProcessAudit -v latest -l $DB_JDBC_URL -u $DB_USR_WEBM -p "$DB_PWD_WEBM" -tsdata WEBMDATA -tsindex WEBMINDX
./dbConfigurator.sh -a create -d oracle -c ProcessEngine -v latest -l $DB_JDBC_URL -u $DB_USR_WEBM -p "$DB_PWD_WEBM" -tsdata WEBMDATA -tsindex WEBMINDX
./dbConfigurator.sh -a create -d oracle -pr TN -v latest -l $DB_JDBC_URL -u $DB_USR_WEBMTN -p "$DB_PWD_WEBMTN" -tsdata WEBMDATA -tsindex WEBMINDX

The next step shown in documentation would be to run webMethods1015/MWS/server/default/bin/mws.sh init
However when doing so, I receive the following error.

image
image1229Ă—307 10.8 KB

Is there a solution that does not involve rebuilding the WEBM/WEBMTN schemas?

2

I am not sure if the error you posted has enough information to provide a clue. Since it is a brand new install I would recommend you recreate the MWS tables and update the softwareAG1015\MWS\server\default\config\mws.db.xml config with the DB password (in plain text) and then save it. After this start the MWS again.

The very first time it will take a while to bootup MWS. Another thing to do is to apply the latest MWS fix and the DCC fix (before creating MWS tables).

1 Like
3

Is there any other node in your cluster or is this the first node you are building? The rest of the _full_.log and wrapper.log files would be useful here. Check the cluster.xml file if there is a ghost node there. Looks like something is wrong with one of the cluster nodes but there aren’t enough information to understand what.

1 Like
4

Hi,

additional information regarding the db compontents:
I recommend using three different oracle db users/schemas here:

  • IS&BPM
  • MWS
  • TN (already separated as I can see in your original post.)

Additionally, instead of just creating the ProcessAudit and ProcessEngine components separately, you should use the “BPM” product instead.
Remember to create an additional user/schema for the “Archive” component, otherwise you won´t be able to delete/archive the IS Audit and Process Audit data later on.
See Monitor Users Guide for further informations on this.

Furthermore, I cannot see any information how the Tablespaces and the Users were created prior to running the above mentioned commands. Can you add these informations, please?

Regards,
Holger

5

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.