After you upgrade Replication Server version 15.0 and its user databases, and set the system version to 1102 or higher, you must set the Replication Server site version to the new software version level before you can use the new Replication Server features.
Refer to What’s New in Replication Server 15.0? and the Replication Server release bulletin for more information about new features.
Once you set the replication system version to a new level, you cannot downgrade any Replication Servers in the replication system below that version level or install a Replication Server below that version level.To return to an earlier software version, you must reinstall all Replication Servers and re-create your replication applications.
If you do not want to use new features that depend on the site version, do not set the Replication Server site version after the upgrade. Then you can downgrade to an earlier version if needed.
create, alter,
and drop replication definitions are not allowed
until you set the Replication Server site version to 1200 or higher.
Setting the Replication Server site version to
15.0
Log in to the current Replication Server.
Execute this command:
sysadmin site_version, 1500
The Replication Server release bulletin may instruct you to set the site version to a more recent version level.
Once you have set the Replication Server site version,
you cannot downgrade the Replication Server. To return to an earlier
software version, you must reinstall the Replication Server and
re-create any aspects of your replication applications
that pertain to that Replication Server.
After you upgrade a Replication Server, set its site version to 1500, and perform route upgrades to the relevant routes, use the Adaptive Server commands dump database or dump transaction to back up the RSSD and the Replication Server sysadmin erssd, backup command to back up the ERSSD.
You can restore the RSSD with the Adaptive Server commands load database or load transaction or restore the ERSSD using the ERSSD recovery procedure. See Chapter 4, “Managing a replication system” in the Replication Server Administration Guide, for information on recovery procedure. If you have a current backup, you can avoid potential problems from loading an RSSD that corresponds to an earlier version level. After you load the backup, all queued messages from other Replication Servers can be recognized by this Replication Server and RSSD.
If you restore the RSSD from a backup performed before you set the site version, messages that the RSSD cannot accept might arrive at the Replication Server.
You can use new Relication Server features that interact with other Replication Servers only if all these things are true:
The system version has been set to 1102.
The site version for both Replication Servers has been set to the current version.
The routes between the Replication Servers have been upgraded.
See “Setting the replication system version” and “Upgrading routes” for more information.
For example, Replication Servers with a site version set to version 15.0 can create replication definitions for tables containing bigint datatype. Such replication definitions are distributed to other Replication Servers with site versions that are at the same version level or higher. Replication Servers of earlier versions do not receive information about these replication definitions.
