The route version is the lower of the two site version numbers of the source and destination Replication Servers of the route.
Replication Server version 11.5 or later uses route version information to determine which feature set you can use with the route and which data to propagate to other sites. If the route version is lower than the earliest site version, you must perform a route upgrade. For example, information necessary for version 15.5 features is not propagated to other sites until the corresponding route versions are upgraded to 1550.
Upgrade any routes for which the upgraded Replication Server is the source or destination server, and the site versions of the source and destination servers are at version 1550 or higher.
After you upgrade to Replication Server 15.5 and set the site version to 1550, you must upgrade each route for which this Replication Server is a source or destination, and the site versions of the source and destination are at 1550 or later. How you upgrade routes depends on how you use Replication Server, and whether you are using a mixed-version system. See “Mixed-version replication system”.
Replication Server uses the Replication Manager (RM) plug-in to upgrade routes. RM provides a list of all the routes that require an upgrade. You can select a single route to be updated.
See Chapter 6, “Managing Routes” in the Replication Server Administration Guide Volume 1. For a full description of the route upgrade commands, see Chapter 3, “Replication Server Commands” in the Replication Server Reference Manual.
After you upgrade the route, you must restart the primary Replication Server distributor thread to support the replication of features included with the new version of Replication Server. For example, to restart primary data server—PDS, and primary database—pdb:
suspend distributor PDS.pdb go resume distributor PDS.pdb go
