Limitations

When you are using the Rebase (ReSync) procedures to synchronize the RealTime databases (RTDB) between zones, the following limitations will apply:

• The Rebase (ReSync) procedures only cover the RTDB. The easy eXtended Operator (ezXOS) display files will not be synchronized with these procedures and will not affect the display SQLite database in any way. The same rollback ability of display files that existed before the Rebase procedures were performed will exist after the Rebase procedures are performed.

• The loadblankdb command will delete the local change tracking database (RealTime.SQLite) to ensure only new changes will be tracked. This will clear all existing changesets and the history of previous program input files. As a result, any package using input files promoted after running this command will behave as if it is the first time being promoted, with no previous version to roll back to.

  In this scenario, you will have two options if you want the capability to promote modifications and still retain the capability to revert back to the original version.

  Note: Both options make the assumption that the original version of the file is known and available.

  • Option 1: Promote the modified file first. This will not have rollback capability. If the changes are not desired, then promote the original file. This will have rollback capability to the modified file, but should not be needed because it is already a known "good" version.

  • Option 2: Promote the original file first. This will not have rollback capability, but should not be needed because it will not be any different than what currently exits in the database. Then promote the modified file. This will have rollback capability to the original file.