Installation FAQs and Troubleshooting

This section can help you troubleshoot some common error messages that you might receive.

What might I do if the Enterprise Message Service destination creation fails when configuring TIBCO Order Management?

If TIBCO Enterprise Message Service is not installed on the same machine as TIBCO Order Management, the destination creation fails. Create the destinations manually by using the Enterprise Message Service Administration utility on the machine where Enterprise Message Service is installed.

For details, see $OM_HOME/ems/AF_CreateEMSChannel.txt

What might I do when I get the "ORA-00942: table or view does not exist" error. I have created Order Management Server database by using the Database Wizard and see the tables created correctly in the database. What could be the problem?

Ensure you have configured the hibernate.default_catalog property correctly. This property can be configured through the Configurator UI and is located at the following path: "Order management System -> Member 1 -> Persistence -> hibernate.default_catalog. The value of this property might be the database user name of the Order Management Server database.

What might I do if I get the following error related to the Oracle driver?

SEVERE: Error when registering Oracle JDBC Diagnosability MBean.

javax.management.MalformedObjectNameException: Invalid character ' ' in value part of property

at javax.management.ObjectName.construct(ObjectName.java:602)

at javax.management.ObjectName.<init>(ObjectName.java:1394)

This could be an Oracle driver issue. Try downloading the drivers from OTN again. A patch has been added for fixing this issue. To know whether you have the patch, run:

What might I do to get the Hibernate component if the servers where TIBCO Order Management is deployed does not have Internet connectivity?

Download the product_tibco_hibernate_3.6.9.001.zip file from the http://public.tibco.com/pub/tibco_oss/hibernate/product_tibco_hibernate_3.6.9.001.zip location.

What might I do if I see the ORACLE related errors during migration?

Set of ORACLE errors are bound to occur if other scripts have already been run. For example, purge scripts. Such ORACLE errors have been added to the ignore list and they do not cause the migration to fail. However, any error other than the defined list results in the database migration failure.

All the errors are logged in the $OM_HOME/migration/log/DBmigration<<dd-mm-yyhr:min:dec>>.log file:

What might I do to upgrade Enterprise Message Service from version X to 8.x.x?

Ensure you back up all the data store and configuration files before performing any upgrade.

For a single Enterprise Message Service server, perform the following steps:

Steps to upgrade the Enterprise Message Service server:

1. Disconnect all your applications connecting to the current Enterprise Message Service versions.
2. Stop the Enterprise Message Service server.
3. Back up all the configuration files and the data store for the Enterprise Message Service server.
4. Uninstall the current version of the Enterprise Message Service server.
   Note: You can skip this step if you want to have multiple Enterprise Message Service server versions on the box. It is not a good practice to follow.
5. Install Enterprise Message Service server 8.x.x.
6. Update the environment variables accordingly on the Enterprise Message Service server box to reflect the new Enterprise Message Service installation path.
   Note: Enterprise Message Service 8.x.x is installed in the $TIBCO_HOME/ems/8.x folder. Ensure that you modify the environment variables set for the Enterprise Message Service servers and other applications accordingly.
7. Start the Enterprise Message Service server against your old configuration files and data store.
8. Start all the applications that you want to connect to the Enterprise Message Service server.

If you have set up the Enterprise Message Service server to work on Fault Tolerant, perform the following steps:

1. Back up the .conf and .db files.
2. Shutdown the standby Enterprise Message Service server (version X) by connecting to it through EMSAdmin and issuing the shutdown command.
   Note: Ensure that you are connected to the standby server by executing the info command and verifying the state before issuing the shutdown command.
3. Restart the standby version 8.x.x Enterprise Message Service server having the same configuration setup as that of the standby server. This locks the database files and becomes the standby server. The standby server then runs with the Enterprise Message Service version X.
4. Shutdown active version X Enterprise Message Service server by connecting to it through EMSAdmin and issuing the shutdown command.
   Note: This step activates the standby server, resulting in the shared state conversion to the 8.x.x version. The active server then runs with the 8.x.x version.
5. View the active server log file to verify that the original standby server has been successfully activated.
6. To ensure that applications remain connected and they are processing messages, wait for a few minutes.
7. Restart the previously active Enterprise Message Service server in standby mode with the 8.x.x Enterprise Message Service version with the same configuration file of the previous active Enterprise Message Service server (version X).
8. To failback to the original server, shut down the active server.
   Note: This step is optional. To ensure that both the Enterprise Message Service servers can become active during failover, start the standby Enterprise Message Service server to make both Enterprise Message Service servers run in FT mode.

What might I do if I get the following error message? "Resource Bundle Not found as per locale - java.util.MissingResourceException: Can't find bundle for base name com.tibco.mdm.properties.activecatalog.HierarchyMessages" in OMS-UI startup logs.

Ignore this message

What might I do if I want to run the spring boot service on IPv4 only?

export _JAVA_OPTIONS="-Djava.net.preferIPv4Stack=true"