Newsletter

Dear eXLerate 2016 user,
 
A database synchronization issue has been identified in eXLerate 2016. This holds for both the eXLerate 4.0.0 and eXLerate 4.0.1 releases and only affects systems with multiple eXLerate server computers. Systems with a standalone computer and systems running eXLerate 2010 are not affected by this issue.
 
PROBLEM
When a stand-by server is started, the database gets synchronized from the duty server correctly. However, after this, no changes to the duty server's database end up in the stand-by server's database. This means that switching the duty role could result in loss of data. For basic systems without any custom database functionality, these data comprise the event history (only the database entries; log file entries, if any, will still be present).
 
SOLUTION
For eXLerate 2016 systems with redundant servers we strongly suggest you to update your systems with the patch release (eXLerate 4.0.2) available on our website (http://www.spiritit.com/support/downloads).
When applying this update, please use the following steps in order to minimize risk of losing data:

1. Identify the current duty server
2. Shut down eXLerate (application + control center) on all servers
3. Install the patch release on the original duty server
4. Remove the ‘command_log’ table from the original duty server. This means removing command_log.* from the application’s database folder, e.g. ‘c:\xlrx\database\exlerate’ (*).
5. Restart the original duty server
6. Once the duty server is up-and-running, repeat steps 3-5 on the other server(s)

Note that eXLerate client systems don't make use of an internal synchronized database. The patch release can be installed on these after all the eXLerate server systems have been updated.

(*): if you have an external database configured in your application and also configured the ‘enable_sync’ for this database via the ‘exSetDatabaseProperty’ worksheet function, you should use an external tool (e.g. HeidiSql for an external MySQL database) to browse through the database content and manually remove the ‘command_log’ table from there.

Go to download