and Upgrading

The server nodes in your Enterprise Replication (ER) domain can run different versions and fixpack levels. On the other hand, new features might only be available between servers running the new version, and administrative ‘cdr’ commands should be run from the newest version environment.

If the server being upgraded is running Enterprise Replication in combination with High-availability cluster replication (HDR, RSS, SDS), the cluster acts as one ER server and ER will be active only on the respective cluster primary. Should this primary role change during the cluster upgrade, so would the active ER server. This should be considered particularly when planning an online cluster upgrade to minimize downtime, likely with the intention to also have ER replicating throughout the process.

There is no immediate requirement to upgrade the various servers in your Enterprise Replication domain in any coordinated manner. Should the newer version provide any new or improved functionality, this might be available only on or between servers running this version; as far as the novelty is restricted to the "cdr" command line utility, it might be sufficient to use the new version's utility in order to enable the functionality across more servers.

Note: When upgrading only a subset of servers to version 15.x, especially if LARGE tables (see also SMALL and LARGE tables) are meant to participate in replication, only the version 15.x "cdr" utility will be able to work with these tables, for instance when defining, checking or syncing replicates.

When upgrading a server running ER, ER must explicitly be stopped before starting the upgrade process, and restarted manually only once all conversion steps are completed successfully.

These topics describe the additional tasks that you must perform when upgrading to and reverting from Version 15.0.0 if you are running .