Upgrading Routes

Set the route version to the new version.

1. Execute admin version, "route" to report the routes that you need to upgrade that start from and go to the Replication Server you are upgrading. An example of the report:

   Source  Destination  Route    Proposed  Status

                        Version  Version

   ------  -----------  -------  --------  ------------------

   NY_RS   LON_RS        1500    1550      Need route upgrade

2. Execute sysadmin upgrade, "route", dest_rs_name on the Replication Server that originates the route you want to upgrade where dest_rs_name is the destination Replication Server of the route you are upgrading. The user ID and password you use to execute the command must also exist at the destination Replication Server, and the RSSD of the destination Replication Server. This user ID must have sa permission at the destination Replication Server and dbo permission at the RSSD of the destination Replication Server. For example, to upgrade the route from NY_RS to LON_RS in the example replication system in step 1, execute:

   sysadmin upgrade, "route", LON_RS

   When you execute the command, you see the message:

   Route upgrade for route 'NY_RS.LON_RS' is in progress in the background"

   In the background, NY_RS starts a routing thread that performs these procedures:
   • NY_RS determines if the route upgrade requires RSSD materialization. If it does, NY_RS proceeds to the next step. Otherwise, NY_RS places a commit marker in the RSSD of LON_RS to alter the route version and completes the route upgrade.
   • NY_RS places a begin marker in the RSSD of NY_RS.
   • NY_RS checks every two seconds for the arrival of the begin marker at the RSSD of LON_RS. If the begin marker does not arrive at the RSSD of LON_RS within the defined threshold of one minute, NY_RS terminates the upgrade process.
   • When the begin marker arrives at the RSSD of LON_RS, NY_RS instructs LON_RS to enter hibernation mode.
   • The command instructs NY_RS to process the set of route upgrade scripts.
   • NY_RS places a commit marker in the RSSD of LON_RS to alter the route version and then NY_RS completes the route upgrade.
   • NY_RS instructs LON_RS to leave the hibernation mode.
3. Execute admin version, "route" to check the status of the route upgrade. If:
   • The route upgrade succeeds, the route should not be listed in the output.

   • The route upgrade fails and you need to recover the route from the upgrade, you see something similar to:

     Source  Destination  Route    Proposed  Status

                          Version  Version

     ------  -----------  -------  --------  ----------------

     NY_RS   LON_RS       1500     1550      need route

                                             upgrade recovery

   • If the route upgrade did not proceed and if there are still routes that you need to upgrade, you see something similar to:

     Source  Destination  Route    Proposed  Status

                          Version  Version

     ------  -----------  -------  --------  ----------------

     NY_RS   ROM_RS       1500     1550      need route

                                             upgrade

   You can also check the error log of source_rs_name, the Replication Server where the route starts, for the status of the route upgrade. In a:

   • Successful route upgrade that includes materialization to make information associated with new features available to a newly upgraded Replication Server:

     Upgrade for route 'source_rs_name.dest_rs_name' is complete.

   • Successful route upgrade that does not need rematerialization:

     Upgrade for route 'source_rs_name.dest_rs_name' is complete. no copying of RSSD information is necessary.

   • Failed route upgrade:

     Route upgrade/upgrade recovery fails due to error. The upgrade procedure is not completed. This routing thread will in turn exit.
4. To recover the route upgrade if the route upgrade fails:
   1. Execute sysadmin upgrade,"route", dest_rs , "recovery" at the source Replication Server. For example, at NY_RS, execute:

      sysadmin upgrade, "route", LON_RS, "recovery"

   2. Execute admin version, "route" at NY_RS to verify that the route upgrade is completed.
5. Restart the primary Replication Server distributor thread connection from the primary database after you upgrade the route to support the replication of features included with the new version of Replication Server.
   For example, to restart the thread from the primary data server— PDS, and primary database—pdb, enter:

   suspend distributor PS.pdb
   go
   resume distributor PDS.pdb
   go