During the upgrade from EMS 4 to EMS 5, is the underlying datastore changed?
Article ID: KB0088398
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
The datastore format will be changed. However, this is done internally in EMS 5.x server during server startup.
EMS 5.x is fully backward compatible with EMS 4.x. So you could use 4.x datastore to start EMS 5.x server. EMS 5.x will convert the datastore format from 4.x to 5.x automatically. You will see something similar to the following when you start EMS 5.x with the 4.x datastore.
================
2008-12-03 13:53:30.974 Converting datastore\async-msgs.db format from 4.4.0 to 5.0.0
2008-12-03 13:53:30.974 Converting datastore\meta.db format from 4.4.0 to 5.0.0
2008-12-03 13:53:30.974 Converting datastore\sync-msgs.db format from 4.4.0 to 5.0.0
2008-12-03 13:53:30.994 Server is active.
================
Furthermore, if you upgrade from EMS 4.x to 5.x, tibesmd makes some changes to your store files that allow them to function with the multiple store feature. These changes are incompatible with 4.x, and will prevent a 4.x server from starting if you try to roll back to an older version of EMS. The tibemsdb5revert tool is included with EMS in order to remove the changes made to those files. The tool takes one argument, which is the directory where the store files are located. By default, the files are in the tibemsd working directory.
You must give the absolute path to the directory. For example:
tibemsdb5revert /filesystem/datastore
Run tibemsdb5revert after reverting to 4.x, but before restarting the EMS server. The tool only makes changes to default store files, sync-msgs.db, async-msgs.db, and meta.db. If you have altered the default configuration to change these file names, tibemsdb5revert will fail.
For more details, please refer to EMS release notes, section "Compatibility With Previous Versions".
The datastore format will be changed. However, this is done internally in EMS 5.x server during server startup.
EMS 5.x is fully backward compatible with EMS 4.x. So you could use 4.x datastore to start EMS 5.x server. EMS 5.x will convert the datastore format from 4.x to 5.x automatically. You will see something similar to the following when you start EMS 5.x with the 4.x datastore.
================
2008-12-03 13:53:30.974 Converting datastore\async-msgs.db format from 4.4.0 to 5.0.0
2008-12-03 13:53:30.974 Converting datastore\meta.db format from 4.4.0 to 5.0.0
2008-12-03 13:53:30.974 Converting datastore\sync-msgs.db format from 4.4.0 to 5.0.0
2008-12-03 13:53:30.994 Server is active.
================
Furthermore, if you upgrade from EMS 4.x to 5.x, tibesmd makes some changes to your store files that allow them to function with the multiple store feature. These changes are incompatible with 4.x, and will prevent a 4.x server from starting if you try to roll back to an older version of EMS. The tibemsdb5revert tool is included with EMS in order to remove the changes made to those files. The tool takes one argument, which is the directory where the store files are located. By default, the files are in the tibemsd working directory.
You must give the absolute path to the directory. For example:
tibemsdb5revert /filesystem/datastore
Run tibemsdb5revert after reverting to 4.x, but before restarting the EMS server. The tool only makes changes to default store files, sync-msgs.db, async-msgs.db, and meta.db. If you have altered the default configuration to change these file names, tibemsdb5revert will fail.
For more details, please refer to EMS release notes, section "Compatibility With Previous Versions".
Issue/Introduction
During the upgrade from EMS 4 to EMS 5, is the underlying datastore changed?
Feedback
Yes
No
Powered by
