Schema updates from imported packets

Packets exported from the working schema repository may include new schema revisions that require database upgrades at other sites. In this case, the syncreplica –import command cannot finish its process until the user database replica is upgraded to the new schema version.

If a packet contains updates for both the schema repository and the user database replica, syncreplica –import stops the process and prints the following message:
packet_name is destined for schema revision revision_number, not
revision_number; re-execute syncreplica after site admin has upgraded

In this case, you must upgrade the affected user database replica and run syncreplica –import again.

If you have automated your synchronization process, the automation script fails and additional packets that depend on the schema changes cannot be applied.